Mercurial > vim

comparison runtime/doc/terminal.txt @ 20552:74e3316c1d5a

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/388a5d4f20b4b64341d1604aa238cab85827b892 Author: Bram Moolenaar <Bram@vim.org> Date: Tue May 26 21:20:45 2020 +0200 Update runtime files
author Bram Moolenaar <Bram@vim.org>
date Tue, 26 May 2020 21:30:04 +0200
parents 56265f711890
children 661eb972cb22
comparison
equal deleted inserted replaced
20551:f1b23a9643fe 20552:74e3316c1d5a
1 *terminal.txt* For Vim version 8.2. Last change: 2020 Apr 23 1 *terminal.txt* For Vim version 8.2. Last change: 2020 May 24
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
159 terminal windows may be configured using the variable 159 terminal windows may be configured using the variable
160 `g:terminal_ansi_colors`, which should be a list of 16 color names or 160 `g:terminal_ansi_colors`, which should be a list of 16 color names or
161 hexadecimal color codes, similar to those accepted by |highlight-guifg|. When 161 hexadecimal color codes, similar to those accepted by |highlight-guifg|. When
162 not using GUI colors, the terminal window always uses the 16 ANSI colors of 162 not using GUI colors, the terminal window always uses the 16 ANSI colors of
163 the underlying terminal. 163 the underlying terminal.
164 When using `term_start()` the colors can be set with the "ansi_colors" option.
164 The |term_setansicolors()| function can be used to change the colors, and 165 The |term_setansicolors()| function can be used to change the colors, and
165 |term_getansicolors()| to get the currently used colors. 166 |term_getansicolors()| to get the currently used colors.
166 167
167 168
168 Command syntax ~ 169 Command syntax ~
1303 1304
1304 1305
1305 Inspecting variables ~ 1306 Inspecting variables ~
1306 *termdebug-variables* *:Evaluate* 1307 *termdebug-variables* *:Evaluate*
1307 `:Evaluate` evaluate the expression under the cursor 1308 `:Evaluate` evaluate the expression under the cursor
1308 `K` same 1309 `K` same (see |termdebug_map_K| to disable)
1309 `:Evaluate` {expr} evaluate {expr} 1310 `:Evaluate` {expr} evaluate {expr}
1310 `:'<,'>Evaluate` evaluate the Visually selected text 1311 `:'<,'>Evaluate` evaluate the Visually selected text
1311 1312
1312 This is similar to using "print" in the gdb window. 1313 This is similar to using "print" in the gdb window.
1313 You can usually shorten `:Evaluate` to `:Ev`. 1314 You can usually shorten `:Evaluate` to `:Ev`.
1334 available a Terminal window will be opened to run the debugged program in. 1335 available a Terminal window will be opened to run the debugged program in.
1335 1336
1336 *termdebug_use_prompt* 1337 *termdebug_use_prompt*
1337 Prompt mode can be used even when the |+terminal| feature is present with: > 1338 Prompt mode can be used even when the |+terminal| feature is present with: >
1338 let g:termdebug_use_prompt = 1 1339 let g:termdebug_use_prompt = 1
1340 <
1341 *termdebug_map_K*
1342 The K key is normally mapped to :Evaluate. If you do not want this use: >
1343 let g:termdebug_map_K = 0
1339 1344
1340 1345
1341 Communication ~ 1346 Communication ~
1342 *termdebug-communication* 1347 *termdebug-communication*
1343 There is another, hidden, buffer, which is used for Vim to communicate with 1348 There is another, hidden, buffer, which is used for Vim to communicate with