From 949dd14d8b2acfc8feda7410ed35e28a2d895992 Mon Sep 17 00:00:00 2001 From: Sean Dewar Date: Mon, 21 Aug 2023 09:28:58 +0100 Subject: vim-patch:9f2962141514 Runtime(termdebug): Add support to view local and argument variables closes: 12403 https://github.com/vim/vim/commit/9f29621415146abc046471440515e9e34f3e57a1 Rename the existing "s:running" (#16790) to "s:gdb_running" to not clash with the "s:running" introduced in this patch (which instead relates to whether the debugged program is currently running in gdb). Keep the file `:retab`bed as before. Co-authored-by: laburnumT --- runtime/doc/nvim_terminal_emulator.txt | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) (limited to 'runtime/doc') diff --git a/runtime/doc/nvim_terminal_emulator.txt b/runtime/doc/nvim_terminal_emulator.txt index bbcc686207..482b608ef9 100644 --- a/runtime/doc/nvim_terminal_emulator.txt +++ b/runtime/doc/nvim_terminal_emulator.txt @@ -325,7 +325,9 @@ Other commands ~ isn't one *:Asm* jump to the window with the disassembly, create it if there isn't one - + *:Var* jump to the window with the local and argument variables, + create it if there isn't one. This window updates whenever the + program is stopped Events ~ *termdebug-events* @@ -400,6 +402,15 @@ If there is no g:termdebug_config you can use: >vim let g:termdebug_disasm_window = 15 Any value greater than 1 will set the Asm window height to that value. + *termdebug_variables_window* +If you want the Var window shown by default, set the flag to 1. +the "variables_window_height" entry can be used to set the window height: >vim + let g:termdebug_config['variables_window'] = 1 + let g:termdebug_config['variables_window_height'] = 15 +If there is no g:termdebug_config you can use: >vim + let g:termdebug_variables_window = 15 +Any value greater than 1 will set the Var window height to that value. + Communication ~ *termdebug-communication* There is another, hidden, buffer, which is used for Vim to communicate with -- cgit From 92ef2b2bcd4f8082e1b05af0663ffef422461e6a Mon Sep 17 00:00:00 2001 From: Sean Dewar Date: Wed, 23 Aug 2023 09:18:17 +0100 Subject: vim-patch:2ae7ffe0bc3c runtime(termdebug): add frame related commands (vim/vim#12511) implementing `:Frame`, `:Up` and `:Down' https://github.com/vim/vim/commit/2ae7ffe0bc3c3ed9fcae35ef23a2b78908580201 Use maparg() for saving K as it's since been ported (and supports Lua callbacks and the other API fields). Use the 3 argument variant of mapset(), as the single argument one isn't ported yet (v8.2.4861). Co-authored-by: Simon Sobisch --- runtime/doc/nvim_terminal_emulator.txt | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) (limited to 'runtime/doc') diff --git a/runtime/doc/nvim_terminal_emulator.txt b/runtime/doc/nvim_terminal_emulator.txt index 482b608ef9..ff3a5791ca 100644 --- a/runtime/doc/nvim_terminal_emulator.txt +++ b/runtime/doc/nvim_terminal_emulator.txt @@ -317,6 +317,21 @@ 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`. + + Other commands ~ *termdebug-commands* *:Gdb* jump to the gdb window @@ -392,6 +407,14 @@ 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 + 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 + let g:termdebug_config['map_plus'] = 0 < *termdebug_disasm_window* If you want the Asm window shown by default, set the "disasm_window" flag to -- cgit From e3b385bed5d27a3c50687526737e8e146c3abddc Mon Sep 17 00:00:00 2001 From: Sean Dewar Date: Wed, 23 Aug 2023 17:41:21 +0100 Subject: 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 --- runtime/doc/nvim_terminal_emulator.txt | 29 +++++++++++++---------------- 1 file changed, 13 insertions(+), 16 deletions(-) (limited to 'runtime/doc') 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* -- cgit