diff options
| author | Bram Moolenaar <Bram@vim.org> | 2019-05-04 21:08:40 +0200 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2019-05-04 21:08:40 +0200 |
| commit | 9dfa3139198b38b28673e251a3756430065914e9 (patch) | |
| tree | 326cc1873083066be93fdd6aaa00a3c93b3310cc /runtime/doc/pattern.txt | |
| parent | ed5ab2a95972b5ef588bdafab9f197e1dcf0c1df (diff) | |
| download | vim-git-9dfa3139198b38b28673e251a3756430065914e9.tar.gz | |
patch 8.1.1270: cannot see current match positionv8.1.1270
Problem: Cannot see current match position.
Solution: Show "3/44" when using the "n" command and "S" is not in
'shortmess'. (Christian Brabandt, closes #4317)
Diffstat (limited to 'runtime/doc/pattern.txt')
| -rw-r--r-- | runtime/doc/pattern.txt | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/runtime/doc/pattern.txt b/runtime/doc/pattern.txt index 90c33ad01..fc4502d0c 100644 --- a/runtime/doc/pattern.txt +++ b/runtime/doc/pattern.txt @@ -152,6 +152,17 @@ use <Esc> to abandon the search. All matches for the last used search pattern will be highlighted if you set the 'hlsearch' option. This can be suspended with the |:nohlsearch| command. +When 'shortmess' does not include the "S" flag, Vim will automatically show an +index, on which the cursor is. This can look like this: > + + [1/5] Cursor is on first of 5 matches. + [1/>99] Cursor is on first of more than 99 matches. + [>99/>99] Cursor is after 99 match of more than 99 matches. + [?/??] Unknown how many matches exists, generating the + statistics was aborted because of search timeout. + +Note: the count does not take offset into account. + When no match is found you get the error: *E486* Pattern not found Note that for the |:global| command this behaves like a normal message, for Vi compatibility. For the |:s| command the "e" flag can be used to avoid the @@ -301,6 +312,14 @@ triggered. In most cases this should be fine, but if a pattern is in use when it's used again it fails. Usually this means there is something wrong with the pattern. + *E956* +In very rare cases a regular expression is used recursively. This can happen +when executing a pattern takes a long time and when checking for messages on +channels a callback is invoked that also uses a pattern or an autocommand is +triggered. In most cases this should be fine, but if a pattern is in use when +it's used again it fails. Usually this means there is something wrong with +the pattern. + ============================================================================== 2. The definition of a pattern *search-pattern* *pattern* *[pattern]* *regular-expression* *regexp* *Pattern* |