diff options
author | Bram Moolenaar <Bram@vim.org> | 2017-09-02 16:28:36 +0200 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2017-09-02 16:28:36 +0200 |
commit | ef68e4fa528165f8dd63156feeffc1af629b8d8a (patch) | |
tree | 14d8384050c19d4279c316b3fcd43e82ba942734 /runtime | |
parent | 3346cc4ffb459ecddb97a8c19bcc5834afa4dead (diff) | |
download | vim-git-ef68e4fa528165f8dd63156feeffc1af629b8d8a.tar.gz |
patch 8.0.1035: sending buffer lines to terminal doesn't work on MS-Windowsv8.0.1035
Problem: Sending buffer lines to terminal doesn't work on MS-Windows.
Solution: Use CR instead of NL after every line. Make the EOF text work
properly. Add the ++eof argument to :terminal.
Diffstat (limited to 'runtime')
-rw-r--r-- | runtime/doc/eval.txt | 6 | ||||
-rw-r--r-- | runtime/doc/terminal.txt | 20 |
2 files changed, 21 insertions, 5 deletions
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt index b9f3c09b1..e8bf16e4e 100644 --- a/runtime/doc/eval.txt +++ b/runtime/doc/eval.txt @@ -8141,6 +8141,12 @@ term_start({cmd}, {options}) *term_start()* have "%d" where the buffer number goes, e.g. "10split|buffer %d"; when not specified "botright sbuf %d" is used + "eof_chars" Text to send after all buffer lines were + written to the terminal. When not set + CTRL-D is used. For Python use CTRL-Z or + "exit()". For a shell use "exit". A CR + is always added. + {only on MS-Windows} {only available when compiled with the |+terminal| feature} diff --git a/runtime/doc/terminal.txt b/runtime/doc/terminal.txt index 9e903d26a..7be6927a0 100644 --- a/runtime/doc/terminal.txt +++ b/runtime/doc/terminal.txt @@ -133,6 +133,14 @@ Syntax ~ height. ++cols={width} Use {width} for the terminal window width. + ++eof={text} when using [range], text to send after + the last line was written. The default + is to send CTRL-D. A CR is appended. + E.g. for a shell use "++eof=exit" and + for Python "++eof=exit()". Special + codes can be used like with `:map`, + e.g. "<C-Z>" for CTRL-Z. + {only on MS-Windows} If you want to use more options use the |term_start()| function. @@ -141,11 +149,13 @@ When the buffer associated with the terminal is unloaded or wiped out the job is killed, similar to calling `job_stop(job, "kill")` So long as the job is running the window behaves like it contains a modified -buffer. Trying to close the window with `CTRL-W :close` or `CTRL-W :hide` -fails, unless "!" is added, in which case the job is ended. The text in the -window is lost. The buffer still exists, but getting it in a window with -`:buffer` will show an -empty buffer. +buffer. Trying to close the window with `CTRL-W :quit` fails. When using +`CTRL-W :quit!` the job is ended. The text in the window is lost. The buffer +still exists, but getting it in a window with `:buffer` will show an empty +buffer. + +Trying to close the window with `CTRL-W :close` also fails. Using +`CTRL-W :close!` will close the window and make the buffer hidden. You can use `CTRL-W :hide` to close the terminal window and make the buffer hidden, the job keeps running. The `:buffer` command can be used to turn the |