Make Usage info in README a bit more verbose

Author: mfussenegger

README.md

@@ -38,14 +38,42 @@ You'll need to install and configure a debug adapter per language. See
 
 A typical debug flow consists of:
 
-- Setting breakpoints via `:lua require'dap'.toggle_breakpoint()`.
-- Launching debug sessions and resuming execution via `:lua require'dap'.continue()`.
-- Stepping through code via `:lua require'dap'.step_over()` and `:lua require'dap'.step_into()`.
-- Inspecting the state via the built-in REPL: `:lua require'dap'.repl.open()`
-  or using the widget UI (`:help dap-widgets`)
+- Setting breakpoints via `:DapToggleBreakpoint` or `:lua
+  require'dap'.toggle_breakpoint()`.
+- Launching debug sessions and resuming execution via `:DapNew` and
+  `:DapContinue` or `:lua require'dap'.continue()`.
+- Stepping through code via `:DapStepOver`, `:DapStepInto` or the corresponding
+  functions `:lua require'dap'.step_over()` and `:lua
+  require'dap'.step_into()`.
+- Inspecting the state:
+  - Via the built-in REPL: `:lua require'dap'.repl.open()`
+    - Try typing an expression followed by ENTER to evaluate it.
+    - Try commands like `.help`, `.frames`, `.threads`.
+    - Variables with structure can be expanded and collapsed with ENTER on the
+      corresponding line.
+  - Via the widget UI (`:help dap-widgets`). Typically you'd inspect values,
+    threads, stacktrace ad-hoc when needed instead of showing the information
+    all the time, but you can also create sidebars for a permanent display
+  - Via UI extensions:
+    - IDE like: [nvim-dap-ui][15]
+    - Middle ground between the IDE like nvim-dap-ui and the built-in widgets: [nvim-dap-view][nvim-dap-view]
+    - Show inline values: [nvim-dap-virtual-text][7]
 
 See [:help dap.txt](doc/dap.txt), `:help dap-mapping` and `:help dap-api`.
 
+**Tip:**
+
+The arrow keys are good candidates for keymaps to step through code as their
+direction resembles the direction you'll step to.
+
+- Down: Step over
+- Right: Step into
+- Left: Step out
+- Up: Restart frame
+
+You can setup keymaps temporary during a debug session using event listeners.
+See `:help dap-listeners`.
+
 ## Supported languages
 
 In theory all of the languages for which a debug adapter exists should be
@@ -74,14 +102,9 @@ older version. Please update the wiki if you discover outdated examples.
   to extend the debugging experience. Either by improving the UI or by making
   it easier to debug parts of an application.
 
-  - Examples of UI/UX extensions are [nvim-dap-virtual-text][7] and [nvim-dap-ui][15]
-  - Examples for language specific extensions include [nvim-jdtls][8] and [nvim-dap-python][9]
-
-## Extensions
-
-All known extensions are listed in the [Wiki][10]. The wiki is community
-maintained. Please add new extensions if you built one or if you discovered one
-that's not listed.
+  All known extensions are listed in the [Wiki][10]. The wiki is community
+  maintained. Please add new extensions if you built one or if you discovered
+  one that's not listed.
 
 ## Non-Goals
 
@@ -147,4 +170,4 @@ time.
 [13]: https://microsoft.github.io/debug-adapter-protocol/implementors/adapters/
 [15]: https://github.com/rcarriga/nvim-dap-ui
 [demo]: https://user-images.githubusercontent.com/38700/124292938-669a7100-db56-11eb-93b8-77b66994fc8a.gif
-
+[nvim-dap-view]: https://github.com/igorlfs/nvim-dap-view