Lines Matching refs:when

19 is especially useful when messages have been overwritten or truncated.  This
42 The previous command output is cleared when another command produces output.
47 maintainer when you spot a mistake.
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
228 On MS-Windows, this message appears when the output of an external command was
251 some bits were lost when converting text from the internally used UTF-8 to the
256 If there is a backup file, when 'writebackup' or 'backup' is set, it will not
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
317 happens when you use ":w! filename" and a swapfile is found.
361 happen when you have a mark in another file, and some other program has
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
458 This appears when you try to exit Vim while some buffers are changed.  You
462 about a buffer, especially when 'hidden' is set.
467 This appears when executing a shell command while at least one buffer was
503 It also happens when the offset of a rule doesn't fit in the space available.
549 system.  See |+feature-list| for when which feature is available.  The
555 This message appears when Vim is trying to open a swap file and finds it
559 attempting a symlink attack (could happen when editing a file in /tmp or when
568 This message is only given when Vim detects a problem when searching for a
590 memory when editing a big file.  You may want to change the 'directory' option
591 to avoid this error.  This error is not given when 'directory' is empty.  See
598 original file.  It is probably a mistake (e.g., when Visual mode was active
599 when using ":w"), therefore Vim requires using a !  after the command, e.g.:
606 Messages like this appear when starting up.  This is not a Vim problem, your
623 You are editing a file in Vim when it didn't exist, but it does exist now.
625 created file.  This message is not given when 'buftype' is not empty.
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
692 |swap-file|.  It's not directly harmful, but when Vim unexpectedly exits some
694 when this problem persists.
699 This happens when Vim tries to connect to the X server, but the X server does
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
788 These happen when a value or expression is used that does not have the
801 This message is given when there is something on the screen for you to read,
814    works the same way as at the |more-prompt|.  Only works when 'compatible'
816 -> Pressing 'j', 'f', 'd' or <Down> is ignored when messages scrolled off the
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
848 given when the 'more' option is on.  It is highlighted with the |hl-MoreMsg|