Lines Matching refs:This
7 This file contains an alphabetical list of messages and error messages that
18 The ":messages" command can be used to view previously given messages. This
19 is especially useful when messages have been overwritten or truncated. This
37 This is especially useful if you accidentally typed <Space> at the hit-enter
103 This is an internal error. If you can reproduce it, please send in a bug
115 The buffer you requested does not exist. This can also happen when you have
133 This happens when an Ex command executes an Ex command that executes an Ex
152 This means that there are not enough colors available for Vim. It will still
161 This can also be done with a line in your Xdefaults file: >
170 attempt expanding wildcards but this fails. This does NOT mean that no
216 messages or grep output cannot be opened. This can have several causes:
219 directory. This could be fixed by changing 'makeef', but then the make
222 - The 'grepprg' or 'makeprg' could not be executed. This cannot always be
229 to be read, but the command didn't run successfully. This can be caused by
264 This failed and the old swap file is now still used. Mostly harmless.
278 This occurs when Vim is trying to rename a file, but a simple change of file
286 This occurs when Vim cannot read typed characters while input is required.
287 Vim got stuck, the only thing it can do is exit. This can happen when both
293 Reading the error file was not possible. This is NOT caused by an error
316 You are protected from overwriting a file that is being edited by Vim. This
330 buffer. This would result in two versions of the same file.
335 The 'write' option is off. This makes all commands that try to write a file
336 generate this message. This could be caused by a |-m| commandline argument.
348 This is caused by setting an invalid value for the 'scroll', 'scrolljump' or
354 You tried to write a file with the name of a directory. This is not possible.
360 You are using a mark that has a line number that doesn't exist. This can
369 the other way around. It should be used like this: {foo,bar}. This matches
375 This is an internal Vim error. Please try to find out how it can be
382 edited. This protects you from accidentally exiting when you still have more
410 used pattern in a ":substitute" command. This fails when no such command has
411 been used yet. See |/~|. This also happens when using ":s/pat/%/", where the
449 are sure, |abandon| it anyway, and lose all the changes. This can be done by
458 This appears when you try to exit Vim while some buffers are changed. You
467 This appears when executing a shell command while at least one buffer was
494 - 'undolevels' Set to a low value, or to -1 to disable undo completely. This
501 This happens on systems with 16 bit ints: The compiled regexp pattern is
530 command in a recursive way. This is restricted to 'maxmapdepth' levels. This
539 command. The script can then again read another script. This can continue
548 disabled. This depends on how big Vim has chosen to be and the operating
555 This message appears when Vim is trying to open a swap file and finds it
556 already exists or finds a symbolic link in its place. This shouldn't happen,
568 This message is only given when Vim detects a problem when searching for a
591 to avoid this error. This error is not given when 'directory' is empty. See
606 Messages like this appear when starting up. This is not a Vim problem, your
618 This message is only given for the first change after 'readonly' has been set.
625 created file. This message is not given when 'buftype' is not empty.
632 option settings and autocommands you would end up with different text). This
636 This message is not given when 'buftype' is not empty.
656 on disk. This message is not given when 'buftype' is not empty.
662 same but the mode (permissions) have changed. This usually occurs when
672 changes. This message is not given when 'buftype' is not empty.
691 This mostly happens when the disk is full. Vim could not write text into the
699 This happens when Vim tries to connect to the X server, but the X server does
709 backslash in a wrong place. This is often caused by command-line continuation
716 This happens when an Ex command with mandatory argument(s) was executed, but
779 This can only happen when changing the source code, when adding a command in
794 This is an (incomplete) overview of various messages that Vim gives:
801 This message is given when there is something on the screen for you to read,
813 -> Press 'k', <Up>, 'u', 'b' or 'g' to scroll back in the messages. This
822 like pressing <Space>. This makes it impossible to select text though.
827 text then use |g<|. This only works when 'more' is set.
847 This message is given when the screen is filled with messages. It is only
883 This is especially useful if you accidentally typed <Space> at the hit-enter