Mercurial > vim

comparison runtime/doc/terminal.txt @ 13051:a6d3e2081544

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Update runtime files commit https://github.com/vim/vim/commit/f0b03c4e98f8a7184d8b4a5d702cbcd602426923 Author: Bram Moolenaar <Bram@vim.org> Date: Sun Dec 17 17:17:07 2017 +0100 Update runtime files
author Christian Brabandt <cb@256bit.org>
date Sun, 17 Dec 2017 17:30:05 +0100
parents 32531a3eab1f
children 656ab57d1ddc
comparison
equal deleted inserted replaced
13050:2615e7a87cb2 13051:a6d3e2081544
1 *terminal.txt* For Vim version 8.0. Last change: 2017 Nov 17 1 *terminal.txt* For Vim version 8.0. Last change: 2017 Dec 17
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
368 Starting ~ 368 Starting ~
369 *termdebug-starting* 369 *termdebug-starting*
370 Load the plugin with this command: > 370 Load the plugin with this command: >
371 packadd termdebug 371 packadd termdebug
372 < *:Termdebug* 372 < *:Termdebug*
373 To start debugging use `:TermDebug` folowed by the command name, for example: > 373 To start debugging use `:Termdebug` followed by the command name, for example: >
374 :Termdebug vim 374 :Termdebug vim
375 375
376 This opens two windows: 376 This opens two windows:
377
377 gdb window A terminal window in which "gdb vim" is executed. Here you 378 gdb window A terminal window in which "gdb vim" is executed. Here you
378 can directly interact with gdb. The buffer name is "!gdb". 379 can directly interact with gdb. The buffer name is "!gdb".
380
379 program window A terminal window for the executed program. When "run" is 381 program window A terminal window for the executed program. When "run" is
380 used in gdb the program I/O will happen in this window, so 382 used in gdb the program I/O will happen in this window, so
381 that it does not interfere with controlling gdb. The buffer 383 that it does not interfere with controlling gdb. The buffer
382 name is "gdb program". 384 name is "gdb program".
383 385
474 :Over execute the gdb "next" command (:Next is a Vim command) 476 :Over execute the gdb "next" command (:Next is a Vim command)
475 :Finish execute the gdb "finish" command 477 :Finish execute the gdb "finish" command
476 :Continue execute the gdb "continue" command 478 :Continue execute the gdb "continue" command
477 :Stop interrupt the program 479 :Stop interrupt the program
478 480
479 The plugin adds a window toolbar with these entries: 481 If 'mouse' is set the plugin adds a window toolbar with these entries:
480 Step :Step 482 Step :Step
481 Next :Over 483 Next :Over
482 Finish :Finish 484 Finish :Finish
483 Cont :Continue 485 Cont :Continue
484 Stop :Stop 486 Stop :Stop
485 Eval :Evaluate 487 Eval :Evaluate
486 This way you can use the mouse to perform the most common commands. 488 This way you can use the mouse to perform the most common commands. You need
489 to have the 'mouse' option set to enable mouse clicks.
487 490
488 491
489 Inspecting variables ~ 492 Inspecting variables ~
490 *termdebug-variables* 493 *termdebug-variables*
491 :Evaluate evaluate the expression under the cursor 494 :Evaluate evaluate the expression under the cursor