thac0/vim
1
0
Fork 0
forked from aniani/vim
Code

runtime(doc): Tweak documentation style a bit

Browse Source 
closes: #11419

Signed-off-by: h-east <h.east.727@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
This commit is contained in:
h-east 2024-11-09 18:37:32 +01:00 committed by Christian Brabandt
parent 50732c7ba6
commit 624bb83619
No known key found for this signature in database
GPG Key ID: F3F92DA383FDDE09
9 changed files with 71 additions and 70 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
runtime/defaults.vim
View File

@ -1,7 +1,7 @@
" The default vimrc file. " The default vimrc file.
" "
" Maintainer: The Vim Project <https://github.com/vim/vim> " Maintainer: The Vim Project <https://github.com/vim/vim>
" Last Change: 2024 Nov 03 " Last Change: 2024 Nov 09
" Former Maintainer: Bram Moolenaar <Bram@vim.org> " Former Maintainer: Bram Moolenaar <Bram@vim.org>
" "
" This is loaded if no vimrc file was found. " This is loaded if no vimrc file was found.
@ -115,7 +115,7 @@ if 1
\ | execute "normal! g`\"" \ | execute "normal! g`\""
\ | endif \ | endif
" Set the default background for putty to dark. Putty usually sets the " Set the default background for putty to dark. Putty usually sets the
" $TERM to xterm and by default it starts with a dark background which " $TERM to xterm and by default it starts with a dark background which
" makes syntax highlighting often hard to read with bg=light " makes syntax highlighting often hard to read with bg=light
" undo this using: ":au! vimStartup TermResponse" " undo this using: ":au! vimStartup TermResponse"

8
runtime/doc/builtin.txt
View File

@ -1,4 +1,4 @@
*builtin.txt* For Vim version 9.1. Last change: 2024 Nov 06 *builtin.txt* For Vim version 9.1. Last change: 2024 Nov 09
VIM REFERENCE MANUAL by Bram Moolenaar VIM REFERENCE MANUAL by Bram Moolenaar
@ -5203,7 +5203,7 @@ glob({expr} [, {nosuf} [, {list} [, {alllinks}]]]) *glob()*
on {list} on {list}
glob2regpat({string}) *glob2regpat()* glob2regpat({string}) *glob2regpat()*
Convert a file pattern, as used by glob(), into a search Convert a file pattern, as used by glob(), into a search
pattern. The result can be used to match with a string that pattern. The result can be used to match with a string that
is a file name. E.g. > is a file name. E.g. >
@ -5656,7 +5656,7 @@ iconv({string}, {from}, {to}) *iconv()*
Return type: |String| Return type: |String|
id({item}) *id()* id({item}) *id()*
The result is a unique String associated with the {item} and The result is a unique String associated with the {item} and
not with the {item}'s contents. It is only valid while the not with the {item}'s contents. It is only valid while the
{item} exists and is referenced. It is valid only in the {item} exists and is referenced. It is valid only in the
@ -7081,7 +7081,7 @@ matchbufline({buf}, {pat}, {lnum}, {end}, [, {dict}])
Return type: list<dict<any>> or list<any> Return type: list<dict<any>> or list<any>
matchdelete({id} [, {win}) *matchdelete()* *E802* *E803* matchdelete({id} [, {win}) *matchdelete()* *E802* *E803*
Deletes a match with ID {id} previously defined by |matchadd()| Deletes a match with ID {id} previously defined by |matchadd()|
or one of the |:match| commands. Returns 0 if successful, or one of the |:match| commands. Returns 0 if successful,
otherwise -1. See example for |matchadd()|. All matches can otherwise -1. See example for |matchadd()|. All matches can

6
runtime/doc/filetype.txt
View File

@ -1,4 +1,4 @@
*filetype.txt* For Vim version 9.1. Last change: 2024 Oct 21 *filetype.txt* For Vim version 9.1. Last change: 2024 Nov 09
VIM REFERENCE MANUAL by Bram Moolenaar VIM REFERENCE MANUAL by Bram Moolenaar
@ -946,8 +946,8 @@ To enable: >
let g:typst_folding = 1 let g:typst_folding = 1
< <
*g:typst_foldnested* *g:typst_foldnested*
When |TRUE| the Typst filetype plugin will fold nested heading under their parents When |TRUE| the Typst filetype plugin will fold nested heading under their
(default: |TRUE|) parents. (default: |TRUE|)
To disable: > To disable: >
let g:typst_foldnested = 0 let g:typst_foldnested = 0

6
runtime/doc/if_pyth.txt
View File

@ -1,4 +1,4 @@
*if_pyth.txt* For Vim version 9.1. Last change: 2024 Nov 06 *if_pyth.txt* For Vim version 9.1. Last change: 2024 Nov 09
VIM REFERENCE MANUAL by Paul Moore VIM REFERENCE MANUAL by Paul Moore
@ -201,8 +201,8 @@ vim.eval(str) *python-eval*
[{'cmd': '/^eval_expr(arg, nextcmd)$/', 'static': 0, 'name': ~ [{'cmd': '/^eval_expr(arg, nextcmd)$/', 'static': 0, 'name': ~
'eval_expr', 'kind': 'f', 'filename': './src/eval.c'}] ~ 'eval_expr', 'kind': 'f', 'filename': './src/eval.c'}] ~
NOTE: In vim9script, local variables in def functions are not visible NOTE: In Vim9 script, local variables in def functions are not visible
to to python evaluations. To pass local variables to python evaluations, to python evaluations. To pass local variables to python evaluations,
use the {locals} dict when calling |py3eval()| and friends. use the {locals} dict when calling |py3eval()| and friends.
vim.bindeval(str) *python-bindeval* vim.bindeval(str) *python-bindeval*

38
runtime/doc/pattern.txt
View File

@ -1,4 +1,4 @@
*pattern.txt* For Vim version 9.1. Last change: 2024 Jun 18 *pattern.txt* For Vim version 9.1. Last change: 2024 Nov 09
VIM REFERENCE MANUAL by Bram Moolenaar VIM REFERENCE MANUAL by Bram Moolenaar
@ -164,7 +164,7 @@ or auto suspended with nohlsearch plugin. See |nohlsearch-install|.
When 'shortmess' does not include the "S" flag, Vim will automatically show an When 'shortmess' does not include the "S" flag, Vim will automatically show an
index, on which the cursor is. This can look like this: > index, on which the cursor is. This can look like this: >
[1/5] Cursor is on first of 5 matches. [1/5] Cursor is on first of 5 matches.
[1/>99] Cursor is on first of more than 99 matches. [1/>99] Cursor is on first of more than 99 matches.
@ -757,7 +757,7 @@ overview.
\([a-z]\+\)\zs,\1 ",abc" in "abc,abc" \([a-z]\+\)\zs,\1 ",abc" in "abc,abc"
\@123<= \@123<=
Like "\@<=" but only look back 123 bytes. This avoids trying lots Like "\@<=" but only look back 123 bytes. This avoids trying lots
of matches that are known to fail and make executing the pattern very of matches that are known to fail and make executing the pattern very
slow. Example, check if there is a "<" just before "span": slow. Example, check if there is a "<" just before "span":
/<\@1<=span /<\@1<=span
@ -783,7 +783,7 @@ overview.
\(\/\/.*\)\@<!in "in" which is not after "//" \(\/\/.*\)\@<!in "in" which is not after "//"
\@123<! \@123<!
Like "\@<!" but only look back 123 bytes. This avoids trying lots of Like "\@<!" but only look back 123 bytes. This avoids trying lots of
matches that are known to fail and make executing the pattern very matches that are known to fail and make executing the pattern very
slow. slow.
@ -907,7 +907,7 @@ $ At end of pattern or in front of "\|", "\)" or "\n" ('magic' on):
inside the Visual area put it at the start and just before the end of inside the Visual area put it at the start and just before the end of
the pattern, e.g.: > the pattern, e.g.: >
/\%Vfoo.*ba\%Vr /\%Vfoo.*ba\%Vr
< This also works if only "foo bar" was Visually selected. This: > < This also works if only "foo bar" was Visually selected. This: >
/\%Vfoo.*bar\%V /\%Vfoo.*bar\%V
< would match "foo bar" if the Visual selection continues after the "r". < would match "foo bar" if the Visual selection continues after the "r".
Only works for the current buffer. Only works for the current buffer.
@ -1014,7 +1014,7 @@ $ At end of pattern or in front of "\|", "\)" or "\n" ('magic' on):
< To match all characters after the current virtual column (where the < To match all characters after the current virtual column (where the
cursor is): > cursor is): >
/\%>.v.* /\%>.v.*
< Column 17 is not included, because this is a |/zero-width| match. To < Column 17 is not included, because this is a |/zero-width| match. To
include the column use: > include the column use: >
/^.*\%17v. /^.*\%17v.
< This command does the same thing, but also matches when there is no < This command does the same thing, but also matches when there is no
@ -1138,11 +1138,11 @@ x A single character, with no special meaning, matches itself
in the collection: "[^xyz]" matches anything but 'x', 'y' and 'z'. in the collection: "[^xyz]" matches anything but 'x', 'y' and 'z'.
- If two characters in the sequence are separated by '-', this is - If two characters in the sequence are separated by '-', this is
shorthand for the full list of ASCII characters between them. E.g., shorthand for the full list of ASCII characters between them. E.g.,
"[0-9]" matches any decimal digit. If the starting character exceeds "[0-9]" matches any decimal digit. If the starting character exceeds
the ending character, e.g. [c-a], E944 occurs. Non-ASCII characters the ending character, e.g. [c-a], E944 occurs. Non-ASCII characters
can be used, but the character values must not be more than 256 apart can be used, but the character values must not be more than 256 apart
in the old regexp engine. For example, searching by [\u3000-\u4000] in the old regexp engine. For example, searching by [\u3000-\u4000]
after setting re=1 emits a E945 error. Prepending \%#=2 will fix it. after setting re=1 emits a E945 error. Prepending \%#=2 will fix it.
- A character class expression is evaluated to the set of characters - A character class expression is evaluated to the set of characters
belonging to that character class. The following character classes belonging to that character class. The following character classes
are supported: are supported:
@ -1208,7 +1208,7 @@ x A single character, with no special meaning, matches itself
any character that's not in "^]-\bdertnoUux". "[\xyz]" matches '\', any character that's not in "^]-\bdertnoUux". "[\xyz]" matches '\',
'x', 'y' and 'z'. It's better to use "\\" though, future expansions 'x', 'y' and 'z'. It's better to use "\\" though, future expansions
may use other characters after '\'. may use other characters after '\'.
- Omitting the trailing ] is not considered an error. "[]" works like - Omitting the trailing ] is not considered an error. "[]" works like
"[]]", it matches the ']' character. "[]]", it matches the ']' character.
- The following translations are accepted when the 'l' flag is not - The following translations are accepted when the 'l' flag is not
included in 'cpoptions': included in 'cpoptions':
@ -1444,14 +1444,14 @@ Finally, these constructs are unique to Perl:
display you may get unexpected results. That is because Vim display you may get unexpected results. That is because Vim
looks for a match in the line where redrawing starts. looks for a match in the line where redrawing starts.
Also see |matcharg()| and |getmatches()|. The former returns Also see |matcharg()| and |getmatches()|. The former returns
the highlight group and pattern of a previous |:match| the highlight group and pattern of a previous |:match|
command. The latter returns a list with highlight groups and command. The latter returns a list with highlight groups and
patterns defined by both |matchadd()| and |:match|. patterns defined by both |matchadd()| and |:match|.
Highlighting matches using |:match| are limited to three Highlighting matches using |:match| are limited to three
matches (aside from |:match|, |:2match| and |:3match| are matches (aside from |:match|, |:2match| and |:3match| are
available). |matchadd()| does not have this limitation and in available). |matchadd()| does not have this limitation and in
addition makes it possible to prioritize matches. addition makes it possible to prioritize matches.
Another example, which highlights all characters in virtual Another example, which highlights all characters in virtual
@ -1480,7 +1480,7 @@ Finally, these constructs are unique to Perl:
with the lowest number has priority if several match at the with the lowest number has priority if several match at the
same position. It uses the match id 3. same position. It uses the match id 3.
The ":3match" command is used by (Vim < 9.0.2054) |matchparen| The ":3match" command is used by (Vim < 9.0.2054) |matchparen|
plugin. You are suggested to use ":match" for manual matching plugin. You are suggested to use ":match" for manual matching
and ":2match" for another plugin or even better make use of and ":2match" for another plugin or even better make use of
the more flexible |matchadd()| (and similar) functions instead. the more flexible |matchadd()| (and similar) functions instead.
@ -1489,10 +1489,10 @@ Finally, these constructs are unique to Perl:
Fuzzy matching refers to matching strings using a non-exact search string. Fuzzy matching refers to matching strings using a non-exact search string.
Fuzzy matching will match a string, if all the characters in the search string Fuzzy matching will match a string, if all the characters in the search string
are present anywhere in the string in the same order. Case is ignored. In a are present anywhere in the string in the same order. Case is ignored. In a
matched string, other characters can be present between two consecutive matched string, other characters can be present between two consecutive
characters in the search string. If the search string has multiple words, then characters in the search string. If the search string has multiple words, then
each word is matched separately. So the words in the search string can be each word is matched separately. So the words in the search string can be
present in any order in a string. present in any order in a string.
Fuzzy matching assigns a score for each matched string based on the following Fuzzy matching assigns a score for each matched string based on the following
@ -1511,8 +1511,8 @@ will match the strings "GetPattern", "PatternGet", "getPattern", "patGetter",
"getSomePattern", "MatchpatternGet" etc. "getSomePattern", "MatchpatternGet" etc.
The functions |matchfuzzy()| and |matchfuzzypos()| can be used to fuzzy search The functions |matchfuzzy()| and |matchfuzzypos()| can be used to fuzzy search
a string in a List of strings. The matchfuzzy() function returns a List of a string in a List of strings. The matchfuzzy() function returns a List of
matching strings. The matchfuzzypos() functions returns the List of matches, matching strings. The matchfuzzypos() functions returns the List of matches,
the matching positions and the fuzzy match scores. the matching positions and the fuzzy match scores.
The "f" flag of `:vimgrep` enables fuzzy matching. The "f" flag of `:vimgrep` enables fuzzy matching.

4
runtime/doc/pi_netrw.txt
View File

@ -1,4 +1,4 @@
*pi_netrw.txt* For Vim version 9.1. Last change: 2024 Nov 02 *pi_netrw.txt* For Vim version 9.1. Last change: 2024 Nov 09
------------------------------------------------ ------------------------------------------------
NETRW REFERENCE MANUAL by Charles E. Campbell NETRW REFERENCE MANUAL by Charles E. Campbell
@ -1537,7 +1537,7 @@ Associated setting variables:
|g:netrw_nogx| prevent gx map while editing |g:netrw_nogx| prevent gx map while editing
|g:netrw_suppress_gx_mesg| controls gx's suppression of browser messages |g:netrw_suppress_gx_mesg| controls gx's suppression of browser messages
OPENING FILES AND LAUNCHING APPS *netrw-gx* *:Open* *:Launch* {{{2 OPENING FILES AND LAUNCHING APPS *netrw-gx* *:Open* *:Launch* {{{2
Netrw determines which special handler by the following method: Netrw determines which special handler by the following method:

14
runtime/doc/pi_tutor.txt
View File

@ -1,26 +1,26 @@
*pi_tutor.txt* For Vim version 9.1. Last change: 2024 Nov 03 *pi_tutor.txt* For Vim version 9.1. Last change: 2024 Nov 09
INTERACTIVE TUTORIALS FOR VIM *vim-tutor-mode* INTERACTIVE TUTORIALS FOR VIM *vim-tutor-mode*
vim-tutor-mode provides a system to follow and create interactive tutorials vim-tutor-mode provides a system to follow and create interactive tutorials
for vim and third party plugins. It replaces the venerable `vimtutor` system. for vim and third party plugins. It replaces the venerable `vimtutor` system.
============================================================================= =============================================================================
1. Usage *vim-tutor-usage* 1. Usage *vim-tutor-usage*
vim-tutor-mode tutorials are hypertext documents, they have rich text and vim-tutor-mode tutorials are hypertext documents, they have rich text and
contain links. To stand out from the rest of the text, links are underlined. contain links. To stand out from the rest of the text, links are underlined.
You can follow them by placing the cursor over them and pressing <Enter>, or You can follow them by placing the cursor over them and pressing <Enter>, or
by double-clicking them. by double-clicking them.
1.1 Commands 1.1 Commands
------------ ------------
*:Tutor* *:Tutor*
:Tutor {tutorial} Opens a tutorial. Command-line completion for :Tutor {tutorial} Opens a tutorial. Command-line completion for
{tutorial} is provided, the candidates are a list of {tutorial} is provided, the candidates are a list of
'.tutor' files found in the 'tutor/' folder in '.tutor' files found in the 'tutor/' folder in
the 'runtimepath'. Tutorials prefixed with 'vim-' will the 'runtimepath'. Tutorials prefixed with 'vim-'
always be shown first. will always be shown first.
If no {tutorial} is provided, the command starts the If no {tutorial} is provided, the command starts the
'vim-01-beginner' tutorial, which is equivalent to 'vim-01-beginner' tutorial, which is equivalent to
@ -29,7 +29,7 @@ by double-clicking them.
============================================================================= =============================================================================
2. Creating tutorials *vim-tutor-create* 2. Creating tutorials *vim-tutor-create*
Writing vim-tutor-mode tutorials is easy. For an overview of the format used, Writing vim-tutor-mode tutorials is easy. For an overview of the format used,
please consult the 'tutor.tutor' file: > please consult the 'tutor.tutor' file: >
:Tutor tutor :Tutor tutor

57
runtime/doc/syntax.txt
View File

@ -1,4 +1,4 @@
*syntax.txt* For Vim version 9.1. Last change: 2024 Oct 22 *syntax.txt* For Vim version 9.1. Last change: 2024 Nov 09
VIM REFERENCE MANUAL by Bram Moolenaar VIM REFERENCE MANUAL by Bram Moolenaar
@ -1679,20 +1679,20 @@ on" command in your .vimrc file.
When you edit an existing Fortran file, the syntax script will assume free When you edit an existing Fortran file, the syntax script will assume free
source form if the fortran_free_source variable has been set, and assumes source form if the fortran_free_source variable has been set, and assumes
fixed source form if the fortran_fixed_source variable has been set. Suppose fixed source form if the fortran_fixed_source variable has been set. Suppose
neither of these variables have been set. In that case, the syntax script attempts to neither of these variables have been set. In that case, the syntax script
determine which source form has been used by examining the file extension attempts to determine which source form has been used by examining the file
using conventions common to the ifort, gfortran, Cray, NAG, and PathScale extension using conventions common to the ifort, gfortran, Cray, NAG, and
compilers (.f, .for, .f77 for fixed-source, .f90, .f95, .f03, .f08 for PathScale compilers (.f, .for, .f77 for fixed-source, .f90, .f95, .f03, .f08
free-source). No default is used for the .fpp and .ftn file extensions because for free-source). No default is used for the .fpp and .ftn file extensions
different compilers treat them differently. If none of this works, then the because different compilers treat them differently. If none of this works,
script examines the first five columns of the first 500 lines of your file. If then the script examines the first five columns of the first 500 lines of your
no signs of free source form are detected, then the file is assumed to be in file. If no signs of free source form are detected, then the file is assumed
fixed source form. The algorithm should work in the vast majority of cases. to be in fixed source form. The algorithm should work in the vast majority of
In some cases, such as a file that begins with 500 or more full-line comments, cases. In some cases, such as a file that begins with 500 or more full-line
the script may incorrectly decide that the code is in fixed form. If that comments, the script may incorrectly decide that the code is in fixed form.
happens, just add a non-comment statement beginning anywhere in the first five If that happens, just add a non-comment statement beginning anywhere in the
columns of the first twenty-five lines, save (:w), and then reload (:e!) the first five columns of the first twenty-five lines, save (:w), and then reload
file. (:e!) the file.
Vendor extensions ~ Vendor extensions ~
Fixed-form Fortran requires a maximum line length of 72 characters but the Fixed-form Fortran requires a maximum line length of 72 characters but the
@ -2226,9 +2226,9 @@ define the vim variable 'lace_case_insensitive' in your startup file: >
LF (LFRC) *lf.vim* *ft-lf-syntax* *g:lf_shell_syntax* LF (LFRC) *lf.vim* *ft-lf-syntax* *g:lf_shell_syntax*
*b:lf_shell_syntax* *b:lf_shell_syntax*
For the lf file manager configuration files (lfrc) the shell commands For the lf file manager configuration files (lfrc) the shell commands syntax
syntax highlighting can be changed globally and per buffer by setting highlighting can be changed globally and per buffer by setting a different
a different 'include' command search pattern using these variables: 'include' command search pattern using these variables: >
let g:lf_shell_syntax = "syntax/dosbatch.vim" let g:lf_shell_syntax = "syntax/dosbatch.vim"
let b:lf_shell_syntax = "syntax/zsh.vim" let b:lf_shell_syntax = "syntax/zsh.vim"
@ -2538,9 +2538,10 @@ set "msql_minlines" to the value you desire. Example: >
:let msql_minlines = 200 :let msql_minlines = 200
NEOMUTT *neomutt.vim* *ft-neomuttrc-syntax* *ft-neomuttlog-syntax* NEOMUTT *neomutt.vim* *ft-neomuttrc-syntax*
*ft-neomuttlog-syntax*
To disable the default NeoMutt log colors > To disable the default NeoMutt log colors: >
:let g:neolog_disable_default_colors = 1 :let g:neolog_disable_default_colors = 1
@ -2710,9 +2711,9 @@ specified. Default = 1 >
:let g:pandoc#syntax#codeblocks#embeds#use = 1 :let g:pandoc#syntax#codeblocks#embeds#use = 1
For specify what languages and using what syntax files to highlight embeds. This is a For specify what languages and using what syntax files to highlight embeds.
list of language names. When the language pandoc and vim use don't match, you This is a list of language names. When the language pandoc and vim use don't
can use the "PANDOC=VIM" syntax. For example: > match, you can use the "PANDOC=VIM" syntax. For example: >
:let g:pandoc#syntax#codeblocks#embeds#langs = ["ruby", "bash=sh"] :let g:pandoc#syntax#codeblocks#embeds#langs = ["ruby", "bash=sh"]
@ -3922,7 +3923,7 @@ set "tf_minlines" to the value you desire. Example: >
:let tf_minlines = your choice :let tf_minlines = your choice
< <
TYPESCRIPT *typescript.vim* *ft-typescript-syntax* TYPESCRIPT *typescript.vim* *ft-typescript-syntax*
*typescriptreact.vim* *ft-typescriptreact-syntax* *typescriptreact.vim* *ft-typescriptreact-syntax*
There is one option to control the TypeScript syntax highlighting. There is one option to control the TypeScript syntax highlighting.
@ -5309,9 +5310,9 @@ of colors by using the `:colorscheme` command, for example: >
This is basically the same as > This is basically the same as >
:echo g:colors_name :echo g:colors_name
< In case g:colors_name has not been defined :colo will < In case g:colors_name has not been defined :colo will
output "default". Its palette is defined in the file output "default". Its palette is defined in the file
"$VIMRUNTIME/syntax/syncolor.vim" and is based on "$VIMRUNTIME/syntax/syncolor.vim" and is based on
legacy versions of peachpuff and desert. When compiled legacy versions of peachpuff and desert. When compiled
without the |+eval| feature it will output "unknown". without the |+eval| feature it will output "unknown".
:colo[rscheme] {name} Load color scheme {name}. This searches 'runtimepath' :colo[rscheme] {name} Load color scheme {name}. This searches 'runtimepath'
@ -5721,8 +5722,8 @@ guisp={color-name} *highlight-guisp*
:highlight Comment guifg=#11f0c3 guibg=#ff00ff :highlight Comment guifg=#11f0c3 guibg=#ff00ff
< <
If you are authoring a color scheme and use the same hexadecimal value If you are authoring a color scheme and use the same hexadecimal value
repeatedly, you can define a (lower case) name for it in |v:colornames|. repeatedly, you can define a (lower case) name for it in
For example: > |v:colornames|. For example: >
# provide a default value for this color but allow the user to # provide a default value for this color but allow the user to
# override it. # override it.

4
runtime/doc/undo.txt
View File

@ -1,4 +1,4 @@
*undo.txt* For Vim version 9.1. Last change: 2024 Sep 29 *undo.txt* For Vim version 9.1. Last change: 2024 Nov 09
VIM REFERENCE MANUAL by Bram Moolenaar VIM REFERENCE MANUAL by Bram Moolenaar
@ -183,7 +183,7 @@ g- Go to older text state. With a count repeat that many
g+ Go to newer text state. With a count repeat that many g+ Go to newer text state. With a count repeat that many
times. times.
*:lat* *:later* *:lat* *:later*
:lat[er] {count} Go to newer text state {count} times. :lat[er] {count} Go to newer text state {count} times.
:lat[er] {N}s Go to newer text state about {N} seconds later. :lat[er] {N}s Go to newer text state about {N} seconds later.
:lat[er] {N}m Go to newer text state about {N} minutes later. :lat[er] {N}m Go to newer text state about {N} minutes later.
:lat[er] {N}h Go to newer text state about {N} hours later. :lat[er] {N}h Go to newer text state about {N} hours later.