diff options
| author | Sean Dewar <seandewar@users.noreply.github.com> | 2023-08-23 17:41:21 +0100 |
|---|---|---|
| committer | Sean Dewar <seandewar@users.noreply.github.com> | 2023-08-25 11:05:18 +0100 |
| commit | e3b385bed5d27a3c50687526737e8e146c3abddc (patch) | |
| tree | 28e331d8c7ae25815b95ef70b5ca0dd37747c8de /runtime/doc | |
| parent | 92ef2b2bcd4f8082e1b05af0663ffef422461e6a (diff) | |
| download | rneovim-e3b385bed5d27a3c50687526737e8e146c3abddc.tar.gz rneovim-e3b385bed5d27a3c50687526737e8e146c3abddc.tar.bz2 rneovim-e3b385bed5d27a3c50687526737e8e146c3abddc.zip | |
vim-patch:3d3a9152fa6d
runtime(termdebug): more termdebug fixes and improvements (vim/vim#12892)
- Fix and attempt to simplify :Frame/:Up/:Down documentation.
- Accept a count instead for :Up/:Down/+/-.
- Update the "Last Change" dates.
- Fix a missing :let (caused an error if gdb fails to start).
- Wipe the prompt buffer when ending prompt mode (if it exists and wasn't wiped
by the user first). Avoids issues with stale prompt buffers (such as E95 when
starting a new prompt mode session).
- Kill the gdb job if the prompt buffer is unloaded (similar to what's done for
a terminal buffer). Fixes not being able to start a new termdebug session if
the buffer was wiped by the user, for example.
https://github.com/vim/vim/commit/3d3a9152fa6de7038fdfd6d6de25230ed825552a
Diffstat (limited to 'runtime/doc')
| -rw-r--r-- | runtime/doc/nvim_terminal_emulator.txt | 29 |
1 files changed, 13 insertions, 16 deletions
diff --git a/runtime/doc/nvim_terminal_emulator.txt b/runtime/doc/nvim_terminal_emulator.txt index ff3a5791ca..d0d535566d 100644 --- a/runtime/doc/nvim_terminal_emulator.txt +++ b/runtime/doc/nvim_terminal_emulator.txt @@ -317,19 +317,16 @@ This is similar to using "print" in the gdb window. You can usually shorten `:Evaluate` to `:Ev`. -Navigation in the Stack ~ - *termdebug-variables* *:Frame* - `:Frame` Select the given frame, using either the frame's - stack number, address, or function name. - `:Up` Select the frame that called the current one with an - optional argument to say how many frames to go up. - `+` same (see |termdebug_map_plus| to disable) - `:Down` Select the frame called by the current one with - an optional argument to say how many frames to go down. - `-` same (see |termdebug_map_minus| to disable) - -This is similar to using "print" in the gdb window. -You can usually shorten `:Evaluate` to `:Ev`. +Navigating stack frames ~ + *termdebug-frames* *:Frame* *:Up* *:Down* + `:Frame` [frame] select frame [frame], which is a frame number, + address, or function name (default: current frame) + `:Up` [count] go up [count] frames (default: 1; the frame that + called the current) + `+` same (see |termdebug_map_plus| to disable) + `:Down` [count] go down [count] frames (default: 1; the frame called + by the current) + `-` same (see |termdebug_map_minus| to disable) Other commands ~ @@ -403,17 +400,17 @@ If there is no g:termdebug_config you can use: >vim let g:termdebug_use_prompt = 1 < *termdebug_map_K* -The K key is normally mapped to :Evaluate. If you do not want this use: >vim +The K key is normally mapped to |:Evaluate|. If you do not want this use: >vim let g:termdebug_config['map_K'] = 0 If there is no g:termdebug_config you can use: >vim let g:termdebug_map_K = 0 < *termdebug_map_minus* -The - key is normally mapped to :Down. If you do not want this use: >vim +The - key is normally mapped to |:Down|. If you do not want this use: >vim let g:termdebug_config['map_minus'] = 0 < *termdebug_map_plus* -The + key is normally mapped to :Up. If you do not want this use: >vim +The + key is normally mapped to |:Up|. If you do not want this use: >vim let g:termdebug_config['map_plus'] = 0 < *termdebug_disasm_window* |