Mercurial > vim

comparison runtime/doc/terminal.txt @ 12907:32531a3eab1f v8.0.1330

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.0.1330: MS-Windows: job in terminal can't get back to Vim commit https://github.com/vim/vim/commit/52dbb5ea7fde4a77178bc59e2383ca40df503812 Author: Bram Moolenaar <Bram@vim.org> Date: Tue Nov 21 18:11:27 2017 +0100 patch 8.0.1330: MS-Windows: job in terminal can't get back to Vim Problem: MS-Windows: job in terminal can't get back to Vim. Solution: set VIM_SERVERNAME in the environment. (Yasuhiro Matsumoto, closes #2360)
author Christian Brabandt <cb@256bit.org>
date Tue, 21 Nov 2017 18:15:06 +0100
parents db9ffed7e1fc
children a6d3e2081544
comparison
equal deleted inserted replaced
12906:c63e99d14a0f 12907:32531a3eab1f
1 *terminal.txt* For Vim version 8.0. Last change: 2017 Nov 12 1 *terminal.txt* For Vim version 8.0. Last change: 2017 Nov 17
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
103 < *options-in-terminal* 103 < *options-in-terminal*
104 After opening the terminal window and setting 'buftype' to "terminal" the 104 After opening the terminal window and setting 'buftype' to "terminal" the
105 BufWinEnter autocommand event is triggered. This makes it possible to set 105 BufWinEnter autocommand event is triggered. This makes it possible to set
106 options specifically for the window and buffer. Example: > 106 options specifically for the window and buffer. Example: >
107 au BufWinEnter * if &buftype == 'terminal' | setlocal bufhidden=hide | endif 107 au BufWinEnter * if &buftype == 'terminal' | setlocal bufhidden=hide | endif
108
109 Mouse events (click and drag) are passed to the terminal. Mouse move events
110 are only passed when Vim itself is receiving them. For a terminal that is
111 when 'balloonevalterm' is enabled.
108 112
109 113
110 Size and color ~ 114 Size and color ~
111 *terminal-size-color* 115 *terminal-size-color*
112 See option 'termsize' for controlling the size of the terminal window. 116 See option 'termsize' for controlling the size of the terminal window.
333 Just put the files somewhere in your PATH. You can set the 'winptydll' option 337 Just put the files somewhere in your PATH. You can set the 'winptydll' option
334 to point to the right file, if needed. If you have both the 32-bit and 64-bit 338 to point to the right file, if needed. If you have both the 32-bit and 64-bit
335 version, rename to winpty32.dll and winpty64.dll to match the way Vim was 339 version, rename to winpty32.dll and winpty64.dll to match the way Vim was
336 build. 340 build.
337 341
342 Environment variables are used to pass information to the running job:
343 VIM_SERVERNAME v:servername
344
338 ============================================================================== 345 ==============================================================================
339 2. Remote testing *terminal-testing* 346 2. Remote testing *terminal-testing*
340 347
341 Most Vim tests execute a script inside Vim. For some tests this does not 348 Most Vim tests execute a script inside Vim. For some tests this does not
342 work, running the test interferes with the code being tested. To avoid this 349 work, running the test interferes with the code being tested. To avoid this