New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
本家helpのtypo報告スレ (Vim 9.0) #1387
Comments
via Vim 8.2.5167 diff --git runtime/doc/channel.txt runtime/doc/channel.txt
index b7ae4d430..d320c46a2 100644
--- runtime/doc/channel.txt
+++ runtime/doc/channel.txt
@@ -464,7 +464,7 @@ a close callback to the channel.
To read all normal output from a RAW channel that is available: >
let output = ch_readraw(channel)
-To read all error output from a RAW channel that is available:: >
+To read all error output from a RAW channel that is available: >
let output = ch_readraw(channel, {"part": "err"})
Note that if the channel is in NL mode, ch_readraw() will only return one line
for each call. |
diff --git a/runtime/doc/version9.txt b/runtime/doc/version9.txt
index 323829a59..9326f0b24 100644
--- a/runtime/doc/version9.txt
+++ b/runtime/doc/version9.txt
@@ -27366,7 +27366,7 @@ Files: src/evalfunc.c, src/testdir/test_vim9_builtin.vim
Patch 8.2.4460
Problem: Vim9: wrong error for defining dict function.
Solution: Explicitly check for trying to define a dict function.
- (closes 9827)
+ (closes #9827)
Files: src/errors.h, src/userfunc.c, src/vim9compile.c,
src/testdir/test_vim9_func.vim
|
前々スレに未報告分がいくつか残っていました。 netrw関連: それ以外: 前スレはクローズしてしまいましたが、未報告分は残ってないですよね? |
サラッとチェックしただけなのでもしかしたら残っているかもです。 |
あと、netrwについては報告先がBram氏ではないのとメンテナの対応が微妙(複数回先祖返りしたり...)なので、私が積極的に報告することはないです。 |
via Vim 9.0.0047 with Runtime update diff --git runtime/doc/builtin.txt runtime/doc/builtin.txt
index dc68def41..adcb8ce37 100644
--- runtime/doc/builtin.txt
+++ runtime/doc/builtin.txt
@@ -2777,7 +2777,7 @@ flattennew({list} [, {maxdepth}]) *flattennew()*
float2nr({expr}) *float2nr()*
Convert {expr} to a Number by omitting the part after the
decimal point.
- {expr} must evaluate to a |Float| or a Number.
+ {expr} must evaluate to a |Float| or a |Number|.
Returns 0 if {expr} is not a |Float| or a |Number|.
When the value of {expr} is out of range for a |Number| the
result is truncated to 0x7fffffff or -0x7fffffff (or when |
via Vim 9.0.0047 with Runtime update diff --git runtime/doc/usr_41.txt runtime/doc/usr_41.txt
index 7f9cee487..1cf2fe289 100644
--- runtime/doc/usr_41.txt
+++ runtime/doc/usr_41.txt
@@ -139,7 +139,7 @@ FOUR KINDS OF NUMBERS
Numbers can be decimal, hexadecimal, octal and binary.
A hexadecimal number starts with "0x" or "0X". For example "0x1f" is decimal
-31 and 0x1234 is decimal 4660.
+31 and "0x1234" is decimal 4660.
An octal number starts with "0o", "0O". "0o17" is decimal 15.
|
diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt
index dc68def41..30e38c031 100644
--- a/runtime/doc/builtin.txt
+++ b/runtime/doc/builtin.txt
@@ -981,7 +981,7 @@ autocmd_add({acmds}) *autocmd_add()*
let acmd.bufnr = 5
let acmd.cmd = 'call BufEnterFunc()'
call autocmd_add([acmd])
-
+<
Can also be used as a |method|: >
GetAutocmdList()->autocmd_add()
< |
via Vim 9.0.0057 diff --git runtime/doc/gui_x11.txt runtime/doc/gui_x11.txt
index 942037a64..14ed9f5c9 100644
--- runtime/doc/gui_x11.txt
+++ runtime/doc/gui_x11.txt
@@ -680,7 +680,7 @@ Of these three, Vim uses PRIMARY when reading and writing the "* register
register. Vim does not access the SECONDARY selection.
This applies both to the GUI and the terminal version. For non-X11 systems
-the plus and the star register both us the system clipboard.
+the plus and the star register both use the system clipboard.
Examples: (assuming the default option values)
- Select a URL in Visual mode in Vim. Go to your browser and click the 追記: (2022-11-02: 既に修正されていました) |
from vim-jp/vimdoc-ja-working#1121 diff --git a/runtime/doc/visual.txt b/runtime/doc/visual.txt
index c7163c3ff..76c1fd3e9 100644
--- a/runtime/doc/visual.txt
+++ b/runtime/doc/visual.txt
@@ -510,11 +510,11 @@ mode Vim automatically switches to Visual mode, so that the same behavior as
in Visual mode is effective. If you don't want this use |:xmap| or |:smap|.
One particular edge case: >
- :vnoremap <C-K> <Esc>
+ :vnoremap <C-K> <Esc>
This ends Visual mode when in Visual mode, but in Select mode it does not
work, because Select mode is restored after executing the mapped keys. You
need to use: >
- :snoremap <C-K> <Esc>
+ :snoremap <C-K> <Esc>
<
Users will expect printable characters to replace the selected area.
Therefore avoid mapping printable characters in Select mode. Or use |
via Vim 9.0.0553 diff --git runtime/doc/version9.txt runtime/doc/version9.txt
index 9ec13872a..1e355e42f 100644
--- runtime/doc/version9.txt
+++ runtime/doc/version9.txt
@@ -259,7 +259,7 @@ Support for evaluating Vim expressions in a heredoc. |:let-heredoc|
Support for fuzzy matching:
- a string in a List of strings. |fuzzy-matching|
-- completion support for command line completion using 'wildoptions'
+- completion support for command line completion using 'wildoptions'.
- for |:vimgrep|.
Added support for the |Haiku| OS.
@@ -398,22 +398,22 @@ Update xdiff to version 2.33. Update libvterm to revision 789.
Support 'trim' for Python/Lua/Perl/Tcl/Ruby/MzScheme interface heredoc.
-Add the |t_AU| and |t_8u| termap codes for underline and undercurl. Add the
+Add the |t_AU| and |t_8u| termcap codes for underline and undercurl. Add the
t_fd and t_fe termcap codes for detecting focus events.
Support for indenting C pragmas like normal code. (|cino-P|)
-Add support for defining the syntax fold level (|:syn-foldlevel|)
+Add support for defining the syntax fold level. (|:syn-foldlevel|)
Add support for using \<*xxx> in a string to prepend a modifier to a
-character. (|expr-quote|).
+character. (|expr-quote|)
Add support trimming characters at the beginning or end of a string using
|trim()|.
Make ":verbose pwd" show the scope of the directory. |:pwd-verbose|
-Add the "0o" notation for specifying octal numbers |scriptversion-4|
+Add the "0o" notation for specifying octal numbers. |scriptversion-4|
Support for changing to the previous tab-local and window-local directories
using the "tcd -" and "lcd -" commands. (|:tcd-| and |:lcd-|)
@@ -428,7 +428,7 @@ Add support for executing (|:@|) a register containing line continuation.
Lua support:
- Call Vim functions from Lua (vim.call() and vim.fn()).
- Convert a Lua function and a closure to a Vim funcref so that it can be
- accessed in a Vimscript (|lua-funcref|).
+ accessed in a Vim script (|lua-funcref|).
- Not backwards compatible: Make Lua arrays one based.
- Add support for using table.insert() and table.remove() functions with Vim
lists. |
from vim-jp/vimdoc-ja-working#1138 diff --git a/runtime/doc/filetype.txt b/runtime/doc/filetype.txt
index d04e4ac13..370c0c3fd 100644
--- a/runtime/doc/filetype.txt
+++ b/runtime/doc/filetype.txt
@@ -570,7 +570,7 @@ used.
For example, to set the dialect to a default of "fblite" but still allow for
any #lang directive overrides, use the following command: >
- let g:freebasic_lang = "fblite"
+ let g:freebasic_lang = "fblite"
GIT COMMIT *ft-gitcommit-plugin* |
v0.9.0538 diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt
index 2a953eedf..07280b445 100644
--- a/runtime/doc/vim9.txt
+++ b/runtime/doc/vim9.txt
@@ -1035,7 +1035,7 @@ In Vim9 script one can use the following predefined values: >
`true` is the same as `v:true`, `false` the same as `v:false`, `null` the same
as `v:null`.
-While `null` has the type "special", the other "null_" types have the type
+While `null` has the type "special", the other "null_" values have the type
indicated by their name. Quite often a null value is handled the same as an
empty value, but not always. The values can be useful to clear a script-local
variable, since they cannot be deleted with `:unlet`. E.g.: > |
via Vim 9.0.0701 diff --git runtime/doc/userfunc.txt runtime/doc/userfunc.txt
index 806d8f76b..45cd2f4ed 100644
--- runtime/doc/userfunc.txt
+++ runtime/doc/userfunc.txt
@@ -405,7 +405,7 @@ function to abort. `:defer` can be used to avoid that: >
call Handle('Outfile')
endfunc
-Note that deleting "Outfile" is scheduled before calling system(), since it
+Note that deleting "Outfile" is scheduled before calling `system()`, since it
can be created even when `system()` fails.
The deferred functions are called in reverse order, the last one added is |
項目の不足 via Vim 9.0.0709 diff --git runtime/doc/help.txt runtime/doc/help.txt
index db803ef80..d1af85eff 100644
--- runtime/doc/help.txt
+++ runtime/doc/help.txt
@@ -161,6 +161,8 @@ Programming language support ~
|filetype.txt| settings done specifically for a type of file
|quickfix.txt| commands for a quick edit-compile-fix cycle
|ft_ada.txt| Ada (the programming language) support
+|ft_context.txt| Filetype plugin for ConTeXt
+|ft_mp.txt| Filetype plugin for METAFONT and MetaPost
|ft_ps1.txt| Filetype plugin for Windows PowerShell
|ft_raku.txt| Filetype plugin for Raku
|ft_rust.txt| Filetype plugin for Rust |
from vim-jp/vimdoc-ja-working#1150 (comment) diff --git a/runtime/doc/cmdline.txt b/runtime/doc/cmdline.txt
index 8b3787010..f01a862ba 100644
--- a/runtime/doc/cmdline.txt
+++ b/runtime/doc/cmdline.txt
@@ -804,7 +804,7 @@ always be swapped then.
Count and Range *N:*
-When giving a count before entering ":", this is translated into:
+When giving a count before entering ":", this is translated into: >
:.,.+(count - 1)
In words: The "count" lines at and after the cursor. Example: To delete
three lines: > |
From vim-jp/vimdoc-ja-working#1315 (comment) ピリオド抜け diff --git a/runtime/doc/intro.txt b/runtime/doc/intro.txt
index b19c3067c..cb415baf3 100644
--- a/runtime/doc/intro.txt
+++ b/runtime/doc/intro.txt
@@ -184,7 +184,7 @@ introduce Y2K problems, but those are not really part of Vim itself.
==============================================================================
3. Credits *credits* *author*
-Most of Vim was created by Bram Moolenaar <Bram@vim.org> |Bram-Moolenaar|
+Most of Vim was created by Bram Moolenaar <Bram@vim.org> |Bram-Moolenaar|.
Parts of the documentation come from several Vi manuals, written by:
W.N. Joy |
From vim-jp/vimdoc-ja-working#1334 80桁超え diff --git a/runtime/doc/various.txt b/runtime/doc/various.txt
index 4ee889003..ec2e3fdec 100644
--- a/runtime/doc/various.txt
+++ b/runtime/doc/various.txt
@@ -449,7 +449,8 @@ m *+python/dyn* Python 2 interface |python-dynamic| |/dyn|
m *+python3* Python 3 interface |python|
m *+python3/dyn* Python 3 interface |python-dynamic| |/dyn|
m *+python3/dyn-stable*
- Python 3 interface |python-dynamic| |python-stable| |/dyn|
+ Python 3 interface |python-dynamic| |python-stable|
+ |/dyn|
N *+quickfix* |:make| and |quickfix| commands
N *+reltime* |reltime()| function, 'hlsearch'/'incsearch' timeout,
'redrawtime' option |
From vim-jp/vimdoc-ja-working#1339 80桁超え、ピリオド忘れ、コロン&コンマ忘れ diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 6f38bc02b..a5c58ff33 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -5747,7 +5747,7 @@ A jump table for the options with a short description can be found at |Q_op|.
The 'mousemodel' option is set by the |:behave| command.
- *'mousemoveevent'* *'mousemev'* *'nomousemoveevent'* *'nomousemev'*
+ *'mousemoveevent'* *'mousemev'* *'nomousemoveevent'* *'nomousemev'*
'mousemoveevent' 'mousemev' boolean (default off)
global
{only works in the GUI}
@@ -7996,7 +7996,7 @@ A jump table for the options with a short description can be found at |Q_op|.
This option controls the behavior when switching between buffers.
This option is checked, when
- jumping to errors with the |quickfix| commands (|:cc|, |:cn|, |:cp|,
- etc.)
+ etc.).
- jumping to a tag using the |:stag| command.
- opening a file using the |CTRL-W_f| or |CTRL-W_F| command.
- jumping to a buffer using a buffer split command (e.g. |:sbuffer|,
@@ -8973,10 +8973,10 @@ A jump table for the options with a short description can be found at |Q_op|.
displayed when 'verbosefile' is set.
*'viewdir'* *'vdir'*
-'viewdir' 'vdir' string (default for Amiga "home:vimfiles/view",
+'viewdir' 'vdir' string (default for Amiga: "home:vimfiles/view",
for Win32: "$HOME/vimfiles/view",
for Unix: "$HOME/.vim/view",
- for macOS: "$VIM/vimfiles/view"
+ for macOS: "$VIM/vimfiles/view",
for VMS: "sys$login:vimfiles/view")
global
{not available when compiled without the |+mksession| |
コメント開始桁を揃えた。 diff --git a/runtime/doc/term.txt b/runtime/doc/term.txt
index cb4c67683..35c6b25b9 100644
--- a/runtime/doc/term.txt
+++ b/runtime/doc/term.txt
@@ -744,8 +744,8 @@ For Windows Terminal you can use something like this: >
let &t_SI = "\e[5 q" " blink bar
let &t_SR = "\e[3 q" " blink underline
let &t_EI = "\e[1 q" " blink block
- let &t_ti ..= "\e[1 q" " blink block
- let &t_te ..= "\e[0 q" " default (depends on terminal, normally blink block)
+ let &t_ti ..= "\e[1 q" " blink block
+ let &t_te ..= "\e[0 q" " default (depends on terminal, normally blink block)
endif
{not available when compiled without the |+cursorshape| feature} |
From vim-jp/vimdoc-ja-working#1340 スペース→タブ diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt
index 996f0fbba..a8090f0c8 100644
--- a/runtime/doc/builtin.txt
+++ b/runtime/doc/builtin.txt
@@ -4008,8 +4008,8 @@ getqflist([{what}]) *getqflist()*
text description of the error
type type of the error, 'E', '1', etc.
valid |TRUE|: recognized error message
- user_data
- custom data associated with the item, can be
+ user_data
+ custom data associated with the item, can be
any type.
When there is no error list or it's empty, an empty list is |
from vim-jp/vimdoc-ja-working#1360 80桁超え diff --git a/runtime/doc/vim9class.txt b/runtime/doc/vim9class.txt
index 505cbe62f..7c0fed6ae 100644
--- a/runtime/doc/vim9class.txt
+++ b/runtime/doc/vim9class.txt
@@ -402,7 +402,7 @@ class, for which objects can be created. Example: >
An abstract class is defined the same way as a normal class, except that it
does not have any new() method. *E1359*
- *abstract-method* *E1371* *E1372*
+ *abstract-method* *E1371* *E1372*
An abstract method can be defined in an abstract class by using the "abstract"
prefix when defining the method: >
|
from vim-jp/vimdoc-ja-working#1365
diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt
index 996f0fbba..e98d72777 100644
--- a/runtime/doc/builtin.txt
+++ b/runtime/doc/builtin.txt
@@ -6793,96 +6793,96 @@ printf({fmt}, {expr1} ...) *printf()*
having a different word order, positional arguments may be
used to indicate this. For instance: >
- #, c-format
- msgid "%s returning %s"
- msgstr "waarde %2$s komt terug van %1$s"
+ #, c-format
+ msgid "%s returning %s"
+ msgstr "waarde %2$s komt terug van %1$s"
<
- In this example, the sentence has its 2 string arguments reversed
- in the output. >
+ In this example, the sentence has its 2 string arguments
+ reversed in the output. >
- echo printf(
- "In The Netherlands, vim's creator's name is: %1$s %2$s",
- "Bram", "Moolenaar")
-< In The Netherlands, vim's creator's name is: Bram Moolenaar >
+ echo printf(
+ "In The Netherlands, vim's creator's name is: %1$s %2$s",
+ "Bram", "Moolenaar")
+< In The Netherlands, vim's creator's name is: Bram Moolenaar >
- echo printf(
- "In Belgium, vim's creator's name is: %2$s %1$s",
- "Bram", "Moolenaar")
-< In Belgium, vim's creator's name is: Moolenaar Bram
+ echo printf(
+ "In Belgium, vim's creator's name is: %2$s %1$s",
+ "Bram", "Moolenaar")
+< In Belgium, vim's creator's name is: Moolenaar Bram
Width (and precision) can be specified using the '*' specifier.
In this case, you must specify the field width position in the
argument list. >
- echo printf("%1$*2$.*3$d", 1, 2, 3)
-< 001 >
- echo printf("%2$*3$.*1$d", 1, 2, 3)
-< 2 >
- echo printf("%3$*1$.*2$d", 1, 2, 3)
-< 03 >
- echo printf("%1$*2$.*3$g", 1.4142, 2, 3)
-< 1.414
+ echo printf("%1$*2$.*3$d", 1, 2, 3)
+< 001 >
+ echo printf("%2$*3$.*1$d", 1, 2, 3)
+< 2 >
+ echo printf("%3$*1$.*2$d", 1, 2, 3)
+< 03 >
+ echo printf("%1$*2$.*3$g", 1.4142, 2, 3)
+< 1.414
You can mix specifying the width and/or precision directly
and via positional arguments: >
- echo printf("%1$4.*2$f", 1.4142135, 6)
-< 1.414214 >
- echo printf("%1$*2$.4f", 1.4142135, 6)
-< 1.4142 >
- echo printf("%1$*2$.*3$f", 1.4142135, 6, 2)
-< 1.41
+ echo printf("%1$4.*2$f", 1.4142135, 6)
+< 1.414214 >
+ echo printf("%1$*2$.4f", 1.4142135, 6)
+< 1.4142 >
+ echo printf("%1$*2$.*3$f", 1.4142135, 6, 2)
+< 1.41
*E1500*
You cannot mix positional and non-positional arguments: >
- echo printf("%s%1$s", "One", "Two")
-< E1500: Cannot mix positional and non-positional
- arguments: %s%1$s
+ echo printf("%s%1$s", "One", "Two")
+< E1500: Cannot mix positional and non-positional arguments:
+ %s%1$s
*E1501*
You cannot skip a positional argument in a format string: >
- echo printf("%3$s%1$s", "One", "Two", "Three")
-< E1501: format argument 2 unused in $-style
- format: %3$s%1$s
+ echo printf("%3$s%1$s", "One", "Two", "Three")
+< E1501: format argument 2 unused in $-style format:
+ %3$s%1$s
*E1502*
You can re-use a [field-width] (or [precision]) argument: >
- echo printf("%1$d at width %2$d is: %01$*2$d", 1, 2)
-< 1 at width 2 is: 01
+ echo printf("%1$d at width %2$d is: %01$*2$d", 1, 2)
+< 1 at width 2 is: 01
However, you can't use it as a different type: >
- echo printf("%1$d at width %2$ld is: %01$*2$d", 1, 2)
-< E1502: Positional argument 2 used as field
- width reused as different type: long int/int
+ echo printf("%1$d at width %2$ld is: %01$*2$d", 1, 2)
+< E1502: Positional argument 2 used as field width reused as
+ different type: long int/int
*E1503*
When a positional argument is used, but not the correct number
or arguments is given, an error is raised: >
- echo printf("%1$d at width %2$d is: %01$*2$.*3$d", 1, 2)
-< E1503: Positional argument 3 out of bounds:
- %1$d at width %2$d is: %01$*2$.*3$d
+ echo printf("%1$d at width %2$d is: %01$*2$.*3$d", 1, 2)
+< E1503: Positional argument 3 out of bounds: %1$d at width
+ %2$d is: %01$*2$.*3$d
Only the first error is reported: >
- echo printf("%01$*2$.*3$d %4$d", 1, 2)
-< E1503: Positional argument 3 out of bounds:
- %01$*2$.*3$d %4$d
+ echo printf("%01$*2$.*3$d %4$d", 1, 2)
+< E1503: Positional argument 3 out of bounds: %01$*2$.*3$d
+ %4$d
*E1504*
A positional argument can be used more than once: >
- echo printf("%1$s %2$s %1$s", "One", "Two")
-< One Two One
+ echo printf("%1$s %2$s %1$s", "One", "Two")
+< One Two One
However, you can't use a different type the second time: >
- echo printf("%1$s %2$s %1$d", "One", "Two")
-< E1504: Positional argument 1 type used
- inconsistently: int/string
+ echo printf("%1$s %2$s %1$d", "One", "Two")
+< E1504: Positional argument 1 type used inconsistently:
+ int/string
*E1505*
Various other errors that lead to a format string being
wrongly formatted lead to: >
- echo printf("%1$d at width %2$d is: %01$*2$.3$d", 1, 2)
-< E1505: Invalid format specifier:
- %1$d at width %2$d is: %01$*2$.3$d
+ echo printf("%1$d at width %2$d is: %01$*2$.3$d", 1, 2)
+< E1505: Invalid format specifier: %1$d at width %2$d is:
+ %01$*2$.3$d
*E1507*
This internal error indicates that the logic to parse a
@@ -10177,8 +10177,8 @@ type({expr}) The result is a Number representing the type of {expr}.
Job: 8 |v:t_job|
Channel: 9 |v:t_channel|
Blob: 10 |v:t_blob|
- Class 12 |v:t_class|
- Object 13 |v:t_object|
+ Class: 12 |v:t_class|
+ Object: 13 |v:t_object|
For backward compatibility, this method can be used: >
:if type(myvar) == type(0)
:if type(myvar) == type("") |
from vim-jp/vimdoc-ja-working#1372
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index c91145ce7..a96356bba 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -4809,12 +4809,12 @@ Vim comes bundled with a Vim script library, that can be used by runtime,
script authors. Currently, it only includes very few functions, but it may
grow over time.
-The functions are available as |Vim9-script| as well as using legacy vim
+The functions are available as |Vim9-script| as well as using legacy Vim
script (to be used for non Vim 9.0 versions and Neovim).
*dist#vim* *dist#vim9*
-The functions make use of the autoloaded prefix "dist#vim" (for legacy Vim script and
-Neovim) and "dist#vim9" for Vim9 script.
+The functions make use of the autoloaded prefix "dist#vim" (for legacy Vim
+script and Neovim) and "dist#vim9" for Vim9 script.
The following functions are available:
|
diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt
index b246fcbce..0f5884b65 100644
--- a/runtime/doc/vim9.txt
+++ b/runtime/doc/vim9.txt
@@ -1265,7 +1265,7 @@ level. They cannot be created in a function, also not in a legacy function.
yet. This will report any errors found during
compilation.
-:defc[ompile] MyClass Compile all methods in a class |class-compile|.
+:defc[ompile] MyClass Compile all methods in a class. |class-compile|
:defc[ompile] {func}
:defc[ompile] debug {func}
@@ -1720,8 +1720,8 @@ an example for each category: >
Vim does not have a familiar null value; it has various null_<type> predefined
values, for example |null_string|, |null_list|, |null_job|. Primitives do not
have a null_<type>. The typical use cases for null_<type> are:
-- to `clear a variable` and release its resources;
-- as a `default for a parameter` in a function definition, see |null-compare|.
+- to clear a variable and release its resources;
+- as a default for a parameter in a function definition, see |null-compare|.
For a specialized variable, like `job`, null_<type> is used to clear the
resources. For a container variable, resources can also be cleared by
@@ -1773,7 +1773,7 @@ an empty container, do not use null_<type> in a comparison: >
F(null_list) # output: "null"
F([]) # output: "not null, empty"
F(['']) # output: "not null, not empty"
-The above function takes a `list of strings` and reports on it.
+The above function takes a list of strings and reports on it.
Change the above function signature to accept different types of arguments: >
def F(arg: list<any> = null_list) # any type of list
def F(arg: any = null) # any type
@@ -1791,18 +1791,18 @@ with vim9 null semantics, the programmer may chose to use null_<type> in
comparisons and/or other situations.
Elsewhere in the documentation it says:
- Quite often a null value is handled the same as an
- empty value, but not always
+ Quite often a null value is handled the same as an empty value, but
+ not always
Here's an example: >
vim9script
var s1: list<string>
var s2: list<string> = null_list
echo s1 # output: "[]"
echo s2 # output: "[]"
-
+
echo s1 + ['a'] # output: "['a']"
echo s2 + ['a'] # output: "['a']"
-
+
echo s1->add('a') # output: "['a']"
echo s2->add('a') # E1130: Can not add to null list
< |
Vim 9.1.113 です。 diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index e3a9f2013..929fdf357 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -3091,7 +3091,7 @@ text...
:cons[t] {var-name} = {expr1}
:cons[t] [{name1}, {name2}, ...] = {expr1}
:cons[t] [{name}, ..., ; {lastname}] = {expr1}
-:cons[t] {var-name} =<< [trim] {marker}
+:cons[t] {var-name} =<< [trim] [eval] {marker}
text...
text...
{marker} |
Typoと diff --git a/runtime/doc/testing.txt b/runtime/doc/testing.txt
index 442285dc8..fcd402c02 100644
--- a/runtime/doc/testing.txt
+++ b/runtime/doc/testing.txt
@@ -235,7 +235,7 @@ test_mswin_event({event}, {args}) *test_mswin_event()*
"mouse" mouse event.
"key" keyboard event.
"set_keycode_trans_strategy"
- Change the key transation method
+ Change the key translation method.
"mouse":
Inject either a mouse button click, or a mouse move, event.
@@ -294,7 +294,8 @@ test_mswin_event({event}, {args}) *test_mswin_event()*
"set_keycode_trans_strategy":
|w32-experimental-keycode-trans-strategy|
- Switch the keycode translation method. The supported methods are:
+ Switch the keycode translation method. The supported methods
+ are:
experimental: The method used after Patch v8.2.4807
using ToUnicode() Win API call.
classic: The method used pre Patch v8.2.4807 |
version9.txt の目次 diff --git runtime/doc/version9.txt runtime/doc/version9.txt
index 7b9a3664a..a441e519a 100644
--- runtime/doc/version9.txt
+++ runtime/doc/version9.txt
@@ -34,6 +34,11 @@ Changed |changed-9.1|
Added |added-9.1|
Patches |patches-9.1|
+VERSION 9.2 |version-9.2|
+Changed |changed-9.2|
+Added |added-9.2|
+Patches |patches-9.2|
+
See |vi_diff.txt| for an overview of differences between Vi and Vim 9.0.
See |version4.txt|, |version5.txt|, |version6.txt|, |version7.txt| and |
コードブロックが閉じられておらず、下のモードラインの行もコードブロックとしてハイライトされてしまっているため、ちゃんとコードブロックを閉じておいた方が良さそうだなと。 diff --git a/runtime/doc/indent.txt b/runtime/doc/indent.txt
index fe24505ed..2e57423fb 100644
--- a/runtime/doc/indent.txt
+++ b/runtime/doc/indent.txt
@@ -1261,5 +1261,5 @@ By default, the yaml indent script does not try to detect multiline scalars.
If you want to enable this, set the following variable: >
let g:yaml_indent_multiline_scalar = 1
-
+<
vim:tw=78:ts=8:noet:ft=help:norl: |
文頭ではないので、"GVim" ではなく "gVim" 表記の方が良さそうです。参考: diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt
index 12297261c..05ce97420 100644
--- a/runtime/doc/map.txt
+++ b/runtime/doc/map.txt
@@ -989,7 +989,7 @@ in Insert mode: >
1.12 MAPPING SUPER-KEYS or COMMAND-KEYS *:map-super-keys* *:map-cmd-key*
The Super modifier is available in GUI mode (when |gui_running| is 1) for
-GVim on Linux and MacVim on Mac OS. If you're on a Mac, this represents the
+gVim on Linux and MacVim on Mac OS. If you're on a Mac, this represents the
Command key, on Linux with the GTK GUI it represents the Super key.
The character "D" is used for the Super / Command modifier.
|
文末のピリオド忘れと思われます。 diff --git a/en/builtin.txt b/en/builtin.txt
index ec702201..4ec9fe05 100644
--- a/en/builtin.txt
+++ b/en/builtin.txt
@@ -2543,7 +2543,7 @@ expand({string} [, {nosuf} [, {list}]]) *expand()*
not start with '%', '#' or '<', see below.
For a |:terminal| window '%' expands to a '!' followed by
- the command or shell that is run |terminal-bufname|
+ the command or shell that is run. |terminal-bufname|
When {string} starts with '%', '#' or '<', the expansion is
done like for the |cmdline-special| variables with their |
From vim-jp/vimdoc-ja-working#1475 diff --git a/runtime/doc/autocmd.txt b/runtime/doc/autocmd.txt
index 32094b398..af5e36226 100644
--- a/runtime/doc/autocmd.txt
+++ b/runtime/doc/autocmd.txt
@@ -429,7 +429,7 @@ Name triggered by ~
|SessionLoadPost| after loading a session file
|SessionWritePost| After writing the session file using
- the |:mksession| command.
+ the |:mksession| command
|MenuPopup| just before showing the popup menu
|CompleteChanged| after Insert mode completion menu changed |
文頭の After も after にした方がよいかもしれません。 |
--- a/runtime/doc/version9.txt
+++ b/runtime/doc/version9.txt
@@ -32090,7 +32090,7 @@ Solution: Store the text column when d
Patch 9.0.0049
Problem: Csv and tsv files are not recognized.
-Solution: Add patterns fo csv and tsv files. (Leandro Lourenci,
+Solution: Add patterns for csv and tsv files. (Leandro Lourenci,
closes #10680)
Patch 9.0.0050
@@ -40641,7 +40641,7 @@ Solution: Use the class-related grow a
Patch 9.0.1989
Problem: Vim9: double error message given
-Solution: Only give second error message, if ther
+Solution: Only give second error message, if there
wasn't one given before
Patch 9.0.1990
@@ -40687,7 +40687,7 @@ Solution: Mention the defining class f
Patch 9.0.2000
Problem: Vim9: use-after-free in deep call stack
-Solution: Get the objct pointer from execution stack
+Solution: Get the object pointer from execution stack
Patch 9.0.2001
Problem: Vim9: segfault with islocked() |
syntax.txt で小見出しが効いてない、おそらく期待してるのは効くほうだと思うので修正 追記: HTML/OS (by Aestiva) Vim 9.1.0380 diff --git runtime/doc/syntax.txt runtime/doc/syntax.txt
index bfc464534..125483e42 100644
--- runtime/doc/syntax.txt
+++ runtime/doc/syntax.txt
@@ -946,7 +946,7 @@ Enables Stylus for ".astro" files. Default Value: "disable"
NOTE: You need to install an external plugin to support stylus in astro files.
-ASPPERL and ASPVBS *ft-aspperl-syntax* *ft-aspvbs-syntax*
+ASPPERL AND ASPVBS *ft-aspperl-syntax* *ft-aspvbs-syntax*
*.asp and *.asa files could be either Perl or Visual Basic script. Since it's
hard to detect this you can set two global variables to tell Vim what you are |
s/R/r/ diff --git a/runtime/doc/change.txt b/runtime/doc/change.txt
index cd3d6add4..25b028a50 100644
--- a/runtime/doc/change.txt
+++ b/runtime/doc/change.txt
@@ -1346,7 +1346,7 @@ The expression must evaluate to a String. A Number is always automatically
converted to a String. For the "p" and ":put" command, if the result is a
Float it's converted into a String. If the result is a List each element is
turned into a String and used as a line. A Dictionary is converted into a
-String. A FuncRef results in an error message (use string() to convert).
+String. A Funcref results in an error message (use string() to convert).
If the "= register is used for the "p" command, the String is split up at <NL>
characters. If the String ends in a <NL>, it is regarded as a linewise |
空白→タブ diff --git a/runtime/doc/starting.txt b/runtime/doc/starting.txt
index b83a61e00..3f2a1d5ef 100644
--- a/runtime/doc/starting.txt
+++ b/runtime/doc/starting.txt
@@ -104,9 +104,9 @@ rvim vim -Z Like "vim", but in restricted mode (see |-Z|) *rvim*
rview vim -RZ Like "view", but in restricted mode. *rview*
rgvim vim -gZ Like "gvim", but in restricted mode. *rgvim*
rgview vim -RgZ Like "gview", but in restricted mode. *rgview*
-evim vim -y Easy Vim: set 'insertmode' (see |-y|) *evim*
-eview vim -yR Like "evim" in read-only mode *eview*
-vimdiff vim -d Start in diff mode |diff-mode|
+evim vim -y Easy Vim: set 'insertmode' (see |-y|) *evim*
+eview vim -yR Like "evim" in read-only mode *eview*
+vimdiff vim -d Start in diff mode |diff-mode|
gvimdiff vim -gd Start in diff mode |diff-mode|
Additional characters may follow, they are ignored. For example, you can have
@@ -812,7 +812,7 @@ accordingly. Vim proceeds in this order:
Places for your personal initializations:
Unix $HOME/.vimrc, $HOME/.vim/vimrc
- or $XDG_CONFIG_HOME/vim/vimrc
+ or $XDG_CONFIG_HOME/vim/vimrc
MS-Windows $HOME/_vimrc, $HOME/vimfiles/vimrc
or $VIM/_vimrc
Amiga s:.vimrc, home:.vimrc, home:vimfiles:vimrc |
From https://github.com/vim-jp/vimdoc-ja-working/pull/new/hh-update-starting
diff --git a/runtime/doc/starting.txt b/runtime/doc/starting.txt
index b83a61e00..b16fa38e5 100644
--- a/runtime/doc/starting.txt
+++ b/runtime/doc/starting.txt
@@ -1119,7 +1119,7 @@ feature backward compatible). However, if you want to migrate to use
and `~/.vim/vimrc` file.
*xdg-runtime*
-When the |xdg-vimrc| is used the |'runtimepath'| will be modified accordingly
+When the |xdg-vimrc| is used the 'runtimepath' will be modified accordingly
to respect the |xdg-base-dir|: >
"$XDG_CONFIG_HOME/vim,$VIMRUNTIME,/after,$XDG_CONFIG_HOME/vim/after" (2024/05/05) 修正されてた。 |
From vim-jp/vimdoc-ja-working#1507 diff --git a/runtime/doc/term.txt b/runtime/doc/term.txt
index 1256d750d..cdf80c23b 100644
--- a/runtime/doc/term.txt
+++ b/runtime/doc/term.txt
@@ -382,8 +382,8 @@ The options are listed below. The associated termcap code is always equal to
the last two characters of the option name. Only one termcap code is
required: Cursor motion, 't_cm'.
-The options 't_da', 't_db', 't_ms', 't_xs', 't_xn', 't_xo' represent flags in the
-termcap. When the termcap flag is present, the option will be set to "y".
+The options 't_da', 't_db', 't_ms', 't_xs', 't_xn', 't_xo' represent flags in
+the termcap. When the termcap flag is present, the option will be set to "y".
But any non-empty string means that the flag is set. An empty string means
that the flag is not set. 't_CS' works like this too, but it isn't a termcap
flag. |
ここまでをPRed. |
From vim-jp/vimdoc-ja-working#1521
diff --git a/runtime/doc/quickfix.txt b/runtime/doc/quickfix.txt
index f0c1d74d4..e6661df08 100644
--- a/runtime/doc/quickfix.txt
+++ b/runtime/doc/quickfix.txt
@@ -1335,7 +1335,7 @@ passed to make, say :make html or :make pdf.
Additional arguments can be passed to pandoc:
- either by appending them to make, say `:make html --self-contained` .
-- or setting them in `b:pandoc_compiler_args` or `g:pandoc_compiler_args`
+- or setting them in `b:pandoc_compiler_args` or `g:pandoc_compiler_args`.
PERL *quickfix-perl* *compiler-perl*
|
From vim-jp/vimdoc-ja-working#1528 diff --git a/runtime/doc/mbyte.txt b/runtime/doc/mbyte.txt
index e38c30cb1..75b5120a1 100644
--- a/runtime/doc/mbyte.txt
+++ b/runtime/doc/mbyte.txt
@@ -801,7 +801,7 @@ is suitable for complex input, such as CJK.
number of Hira-gana characters are 76. So, first, we pre-input text as
pronounced in Hira-gana, second, we convert Hira-gana to Kanji or Kata-Kana,
if needed. There are some Kana-Kanji conversion server: jserver
- (distributed with Wnn, see below) and canna.Canna can be found at:
+ (distributed with Wnn, see below) and canna. Canna can be found at:
https://osdn.net/projects/canna/
There is a good input system: Wnn4.2. Wnn 4.2 contains, |
本家help(runtime/doc/*.txt)のtypoを報告するスレです。
その都度vim_devに報告するとウザいのである程度溜まってから報告します。
typo発見時のVimバージョン(9.0.xxxx)も添えていただけると助かります。
関連: #1172, #1321
The text was updated successfully, but these errors were encountered: