diff --git a/runtime/doc/cmdline.txt b/runtime/doc/cmdline.txt index 3d63b1964b..9493658ed5 100644 --- a/runtime/doc/cmdline.txt +++ b/runtime/doc/cmdline.txt @@ -788,7 +788,7 @@ An example for subtracting (which isn't very useful): > On this text: 1 one ~ 2 two ~ - 3 three FOLDED~ + 3 three FOLDED ~ 4 four FOLDED ~ 5 five FOLDED ~ 6 six FOLDED ~ diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt index 4f9a3c99f5..41b7d56c69 100644 --- a/runtime/doc/eval.txt +++ b/runtime/doc/eval.txt @@ -2424,7 +2424,7 @@ v:progpath Contains the command with which Vim was invoked, in a form ".exe" is not added to v:progpath. Read-only. - *v:python3_version* *python3-version-variable* + *v:python3_version* *python3-version-variable* v:python3_version Version of Python 3 that Vim was built against. When Python is loaded dynamically (|python-dynamic|), this version diff --git a/runtime/doc/filetype.txt b/runtime/doc/filetype.txt index 987b0d89e9..901711edff 100644 --- a/runtime/doc/filetype.txt +++ b/runtime/doc/filetype.txt @@ -433,7 +433,7 @@ So to enable this only for ruby, set the following variable: > :let g:ruby_exec = 1 If both, the global `plugin_exec` and the `_exec` specific variable -are set, the filetpe specific variable should have precedent. +are set, the filetype specific variable should have precedent. AWK *ft-awk-plugin* diff --git a/runtime/doc/pattern.txt b/runtime/doc/pattern.txt index 9e048ff64a..4fa26e0431 100644 --- a/runtime/doc/pattern.txt +++ b/runtime/doc/pattern.txt @@ -1080,7 +1080,7 @@ match ASCII characters, as indicated by the range. \(\) A pattern enclosed by escaped parentheses. */\(* */\(\)* */\)* E.g., "\(^a\)" matches 'a' at the start of a line. - There can only be ten of these. You can use "\%(" to add more, but + There can only be nine of these. You can use "\%(" to add more, but not counting it as a sub-expression. *E51* *E54* *E55* *E872* *E873* diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt index 17dffa82f7..247dd0992c 100644 --- a/runtime/doc/repeat.txt +++ b/runtime/doc/repeat.txt @@ -1149,8 +1149,8 @@ Profiling should give a good indication of where time is spent, but keep in mind there are various things that may clobber the results: - The accuracy of the time measured depends on the gettimeofday(), or - clock_gettime if available, system function. The accuracy ranges from 1/100 - second to nanoseconds. With clock_gettime the times are displayed in + clock_gettime() if available, system function. The accuracy ranges from + 1/100 second to nanoseconds. With clock_gettime() the times are displayed in nanoseconds, otherwise microseconds. You can use `has("prof_nsec")`. - Real elapsed time is measured, if other processes are busy they may cause diff --git a/runtime/doc/tags b/runtime/doc/tags index 249800fd29..a275352c88 100644 --- a/runtime/doc/tags +++ b/runtime/doc/tags @@ -4458,7 +4458,7 @@ E136 starting.txt /*E136* E1360 vim9class.txt /*E1360* E1361 syntax.txt /*E1361* E1362 vim9class.txt /*E1362* -E1363 vim9class.txt /*E1363* +E1363 vim9.txt /*E1363* E1364 recover.txt /*E1364* E1365 vim9class.txt /*E1365* E1366 vim9class.txt /*E1366* diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt index 1431a134e8..ddcd25503a 100644 --- a/runtime/doc/vim9.txt +++ b/runtime/doc/vim9.txt @@ -1557,7 +1557,7 @@ string to a number. If a type is given where it is not expected you can get *E1272* . -If a type is incomplete you get *E1363*, e.g. when you have an object for +If a type is incomplete you get *E1363* , e.g. when you have an object for which the class is not known (usually that is a null object). Type inference ~ @@ -1756,7 +1756,7 @@ Exporting an item can be written as: > export interface MyClass ... < *E1043* *E1044* As this suggests, only constants, variables, `:def` functions and classes can -be exported. {not implemented yet: class, interface} +be exported. *E1042* `:export` can only be used in Vim9 script, at the script level. @@ -1862,9 +1862,9 @@ However, the namespace cannot be resolved on its own: > < This also affects the use of || in the legacy mapping context. Since || is only a valid prefix for a function and NOT for a namespace, you -cannot use it -to scope a function in a script local namespace. Instead of prefixing the -function with || you should use||. For example: > +cannot use it to scope a function in a script local namespace. Instead of +prefixing the function with || you should use||. For example: +> noremap ,a :call s:that.OtherFunc() < *:import-cycle* diff --git a/runtime/doc/vim9class.txt b/runtime/doc/vim9class.txt index d8bd0328cd..3e5493f203 100644 --- a/runtime/doc/vim9class.txt +++ b/runtime/doc/vim9class.txt @@ -304,7 +304,7 @@ as the first character in the name, and it can be made public by prefixing *class-method* Class methods are also declared with "static". They can use the class variables but they have no access to the object variables, they cannot use the -"this" keyword. +"this" keyword: > class OtherThing this.size: number @@ -656,7 +656,7 @@ When a variable is declared to have the type of an object, but it is not initialized, the value is null. When trying to use this null object Vim often does not know what class was supposed to be used. Vim then cannot check if a variable name is correct and you will get an "Using a null object" error, -even when the variable name is invalid. *E1360* *E1362* *E1363* +even when the variable name is invalid. *E1360* *E1362* Default constructor ~