5
1
I know that there's a command line option to tell vim (or in my case gVim) to output its own log to a file. Unfortunately I can't remember it. Can anybody help?
5
1
I know that there's a command line option to tell vim (or in my case gVim) to output its own log to a file. Unfortunately I can't remember it. Can anybody help?
6
It is the "verbose" option that can be set on startup:
-V[N] Verbose. Sets the 'verbose' option to [N] (default: 10).
Messages will be given for each file that is ":source"d and
for reading or writing a viminfo file. Can be used to find
out what is happening upon startup and exit. {not in Vi}
Example: >
vim -V8 foobar
-V[N]{filename}
Like -V and set 'verbosefile' to {filename}. The result is
that messages are not displayed but written to the file
{filename}. {filename} must not start with a digit.
Example: >
vim -V20vimlog foobar
What do you mean by "its own log"? You can send debug information to a file, but I don't know of any way to log keystrokes, for example, except to record a macro. – garyjohn – 2010-10-19T20:32:51.323
The log contains messages from processing the vimrc file, where it searches for vim files and which files are executed during startup. – Christoph Metzendorf – 2010-10-20T06:51:32.053