Mercurial > vim
diff runtime/doc/starting.txt @ 28435:0533e7466ef0 v8.2.4742
patch 8.2.4742: there is no way to start logging very early in startup
Commit: https://github.com/vim/vim/commit/c9a9a0ac1ec3b985d38c01ddf9f0ba2f15386f34
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Apr 12 15:09:23 2022 +0100
patch 8.2.4742: there is no way to start logging very early in startup
Problem: There is no way to start logging very early in startup.
Solution: Add the --log argument. Include the date in the start message in
the log file. Avoid a duplicate message when forking. Log an
executed shell command.
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Tue, 12 Apr 2022 16:15:03 +0200 |
| parents | d19b7aee1925 |
| children | f73a9bdff3a3 |
line wrap: on
line diff
--- a/runtime/doc/starting.txt +++ b/runtime/doc/starting.txt @@ -344,6 +344,12 @@ a slash. Thus "-R" means recovery and " Example: > vim -V20vimlog foobar < +--log {filename} *--log* + Start logging and write entries to {filename}. + This works like calling `ch_logfile({filename}, 'a')` very + early during startup. + {only available with the +channel feature} + *-D* -D Debugging. Go to debugging mode when executing the first command from a script. |debug-mode| @@ -564,6 +570,7 @@ a slash. Thus "-R" means recovery and " {scriptout} cannot start with a digit. If you want to record what is typed in a human readable for you can use |ch_logfile()|, It adds "raw key input" lines. + Also see |--log|. *-W* -W {scriptout} Like -w, but do not append, overwrite an existing file.