docs: vimdoc parsing errors #36681

Error: .tests/neovim/runtime/doc/dev_test.txt
    (MISSING "`" [420, 79] - [420, 79])
    Error: .tests/neovim/runtime/doc/news.txt
    (MISSING "`" [137, 80] - [137, 80])
    Error: .tests/neovim/runtime/doc/nvim.txt
    (MISSING "<" [106, 0] - [106, 0])
    Error: .tests/neovim/runtime/doc/vimfn.txt
    (MISSING "}" [2610, 26] - [2610, 26])
This commit is contained in:
Justin M. Keyes
2025-11-24 15:10:05 -08:00
committed by GitHub
parent 01a9765035
commit 60c35cc4c7
6 changed files with 24 additions and 22 deletions

View File

@@ -418,8 +418,7 @@ Number; !must be defined to function properly):
Currently only compilers with gcc-compatible arguments are supported. Currently only compilers with gcc-compatible arguments are supported.
- `GDB` (F) (D): makes nvim instances to be run under `gdbserver`. It will be - `GDB` (F) (D): makes nvim instances to be run under `gdbserver`. It will be
accessible on `localhost:7777`: use `gdb build/bin/nvim`, type `target remote accessible on `localhost:7777`: use `gdb build/bin/nvim`, type `target remote :7777` inside.
:7777` inside.
- `GDBSERVER_PORT` (F) (I): overrides port used for `GDB`. - `GDBSERVER_PORT` (F) (I): overrides port used for `GDB`.

View File

@@ -135,8 +135,7 @@ The following new features were added.
API API
• |api-contract| allows existing functions to change return-type from `void => • |api-contract| allows existing functions to change return-type from `void => non-void`.
non-void`.
• |nvim_win_text_height()| can limit the lines checked when a certain • |nvim_win_text_height()| can limit the lines checked when a certain
`max_height` is reached, and returns the `end_row` and `end_vcol` for which `max_height` is reached, and returns the `end_row` and `end_vcol` for which
`max_height` or the calculated height is reached. `max_height` or the calculated height is reached.

View File

@@ -101,6 +101,7 @@ Windows is stored in ~/AppData instead of ~/.config. But you can still share
the same Nvim configuration on all of your machines, by creating the same Nvim configuration on all of your machines, by creating
~/AppData/Local/nvim/init.vim containing just this line: >vim ~/AppData/Local/nvim/init.vim containing just this line: >vim
source ~/.config/nvim/init.vim source ~/.config/nvim/init.vim
<
============================================================================== ==============================================================================
vim:tw=78:ts=8:et:ft=help:norl: vim:tw=78:ts=8:et:ft=help:norl:

View File

@@ -2606,12 +2606,13 @@ fmod({expr1}, {expr2}) *fmod()*
fnameescape({string}) *fnameescape()* fnameescape({string}) *fnameescape()*
Escape {string} for use as file name command argument. All Escape {string} for use as file name command argument. All
characters that have a special meaning, such as `'%'` and `'|'` characters that have a special meaning, such as `'%'` and `'|'`
are escaped with a backslash. are escaped with a backslash. For most systems the characters
For most systems the characters escaped are escaped are: >
" \t\n*?[{`$\\%#'\"|!<". For systems where a backslash \t\n *?[{`$\\%#'\"|!<
appears in a filename, it depends on the value of 'isfname'. < For systems where a backslash appears in a filename, it
A leading '+' and '>' is also escaped (special after |:edit| depends on the value of 'isfname'. A leading '+' and '>' is
and |:write|). And a "-" by itself (special after |:cd|). also escaped (special after |:edit| and |:write|). And a "-"
by itself (special after |:cd|).
Returns an empty string on error. Returns an empty string on error.
Example: >vim Example: >vim
let fname = '+some str%nge|name' let fname = '+some str%nge|name'

View File

@@ -2328,12 +2328,13 @@ function vim.fn.fmod(expr1, expr2) end
--- Escape {string} for use as file name command argument. All --- Escape {string} for use as file name command argument. All
--- characters that have a special meaning, such as `'%'` and `'|'` --- characters that have a special meaning, such as `'%'` and `'|'`
--- are escaped with a backslash. --- are escaped with a backslash. For most systems the characters
--- For most systems the characters escaped are --- escaped are: >
--- " \t\n*?[{`$\\%#'\"|!<". For systems where a backslash --- \t\n *?[{`$\\%#'\"|!<
--- appears in a filename, it depends on the value of 'isfname'. --- <For systems where a backslash appears in a filename, it
--- A leading '+' and '>' is also escaped (special after |:edit| --- depends on the value of 'isfname'. A leading '+' and '>' is
--- and |:write|). And a "-" by itself (special after |:cd|). --- also escaped (special after |:edit| and |:write|). And a "-"
--- by itself (special after |:cd|).
--- Returns an empty string on error. --- Returns an empty string on error.
--- Example: >vim --- Example: >vim
--- let fname = '+some str%nge|name' --- let fname = '+some str%nge|name'

View File

@@ -2957,12 +2957,13 @@ M.funcs = {
desc = [=[ desc = [=[
Escape {string} for use as file name command argument. All Escape {string} for use as file name command argument. All
characters that have a special meaning, such as `'%'` and `'|'` characters that have a special meaning, such as `'%'` and `'|'`
are escaped with a backslash. are escaped with a backslash. For most systems the characters
For most systems the characters escaped are escaped are: >
" \t\n*?[{`$\\%#'\"|!<". For systems where a backslash \t\n *?[{`$\\%#'\"|!<
appears in a filename, it depends on the value of 'isfname'. <For systems where a backslash appears in a filename, it
A leading '+' and '>' is also escaped (special after |:edit| depends on the value of 'isfname'. A leading '+' and '>' is
and |:write|). And a "-" by itself (special after |:cd|). also escaped (special after |:edit| and |:write|). And a "-"
by itself (special after |:cd|).
Returns an empty string on error. Returns an empty string on error.
Example: >vim Example: >vim
let fname = '+some str%nge|name' let fname = '+some str%nge|name'