search

vim-jp / issues

有志で既知のバグや要望を検討・管理し、オフィシャルへの還元をしていきます。
https://vim-jp.org/
341 stars 11 forks source link

本家helpのtypo報告スレ (Vim 9.1) #1433

Open h-east opened 5 months ago

h-east commented 5 months ago

本家help(runtime/doc/*.txt)のtypoを報告するスレです。 その都度vim_devに報告するとウザいのである程度溜まってから報告します。

typo発見時のVimバージョン(9.1.xxxx)も添えていただけると助かります。

関連: #1172, #1321, #1387

h-east commented 5 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1583

diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt
index a82453109..5c1ea3d7b 100644
--- a/runtime/doc/builtin.txt
+++ b/runtime/doc/builtin.txt
@@ -8078,7 +8078,7 @@ pyxeval({expr})                       *pyxeval()*
        See also: |pyeval()|, |py3eval()|

        Can also be used as a |method|: >
-   <       GetExpr()->pyxeval()
+           GetExpr()->pyxeval()
 <
        Return type: any, depending on {expr}

@@ -9486,7 +9486,8 @@ setline({lnum}, {text})                   *setline()*
        Set line {lnum} of the current buffer to {text}.  To insert
        lines use |append()|. To set lines in another buffer use
        |setbufline()|.
-       Any text properties in {lnum} are cleared |text-prop-cleared|.
+       Any text properties in {lnum} are cleared.  See
+       |text-prop-cleared|

        {lnum} is used like with |getline()|.
        When {lnum} is just below the last line the {text} will be
@@ -11039,7 +11040,7 @@ synconcealed({lnum}, {col})             *synconcealed()*
        Note: Doesn't consider |matchadd()| highlighting items,
        since syntax and matching highlighting are two different
        mechanisms |syntax-vs-match|.
-<
+
        Return type: list<any>
h-east commented 5 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1591, https://github.com/vim-jp/vimdoc-ja-working/issues/1590

diff --git a/runtime/doc/change.txt b/runtime/doc/change.txt
index 50ff4ec99..094e29ec1 100644
--- a/runtime/doc/change.txt
+++ b/runtime/doc/change.txt
@@ -1413,7 +1413,7 @@ The next three commands always work on whole lines.
 :[range]m[ove] {address}           *:m* *:mo* *:move* *E134*
            Move the lines given by [range] to below the line
            given by {address}.
-           Any text properties in [range] are cleared
+           Any text properties in [range] are cleared.  See
            |text-prop-cleared|.

 ==============================================================================
h-east commented 4 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1605 80桁超え。

diff --git a/runtime/doc/usr_05.txt b/runtime/doc/usr_05.txt
index d9222594c..134513d77 100644
--- a/runtime/doc/usr_05.txt
+++ b/runtime/doc/usr_05.txt
@@ -455,7 +455,8 @@ Adding nohlsearch package               *nohlsearch-install*
 Load the plugin with this command: >
    packadd nohlsearch
 <
-Automatically execute |:nohlsearch| after 'updatetime' or getting into |Insert| mode.
+Automatically execute |:nohlsearch| after 'updatetime' or getting into
+|Insert| mode.
 Thus assuming default updatetime, hlsearch would be suspended/turned off after
 4 seconds of idle time.
h-east commented 4 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1607

diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt
index 238b7e43d..e3007f542 100644
--- a/runtime/doc/builtin.txt
+++ b/runtime/doc/builtin.txt
@@ -279,8 +279,7 @@ gettabvar({nr}, {varname} [, {def}])
 gettabwinvar({tabnr}, {winnr}, {name} [, {def}])
                any {name} in {winnr} in tab page {tabnr}
 gettagstack([{nr}])        Dict    get the tag stack of window {nr}
-gettext({text} [, {package}])
-               String  lookup translation of {text}
+gettext({text} [, {package}])  String  lookup translation of {text}
 getwininfo([{winid}])      List    list of info about each window
 getwinpos([{timeout}])     List    X and Y coord in pixels of Vim window
 getwinposx()           Number  X coord in pixels of the Vim window
@@ -1225,7 +1224,7 @@ bindtextdomain({package}, {path})         *bindtextdomain()*
        Bind a specific {package} to a {path} so that the
        |gettext()| function can be used to get language-specific
        translations for a package.  {path} is the directory name
-       for the translations. See |package-create|.
+       for the translations.  See |package-create|.

        Return type: none
mityu commented 4 months ago

文と文の間はスペースふたつ入れるということなので。

diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 5f1a2a074..2e1ac94b4 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -5914,17 +5914,17 @@ A jump table for the options with a short description can be found at |Q_op|.
            Using CTRL-X on "0" or CTRL-A on "18446744073709551615"
            (2^64 - 1) has no effect, overflow is prevented.
    blank   If included, treat numbers as signed or unsigned based on
-       preceding whitespace. If a number with a leading dash has its
+       preceding whitespace.  If a number with a leading dash has its
        dash immediately preceded by a non-whitespace character (i.e.,
        not a tab or a " "), the negative sign won't be considered as
        part of the number.  For example:
            Using CTRL-A on "14" in "Carbon-14" results in "Carbon-15"
            (without "blank" it would become "Carbon-13").
            Using CTRL-X on "8" in "Carbon -8" results in "Carbon -9"
-           (because -8 is preceded by whitespace. If "unsigned" was
+           (because -8 is preceded by whitespace.  If "unsigned" was
            set, it would result in "Carbon -7").
        If this format is included, overflow is prevented as if
-       "unsigned" were set. If both this format and "unsigned" are
+       "unsigned" were set.  If both this format and "unsigned" are
        included, "unsigned" will take precedence.

    Numbers which simply begin with a digit in the range 1-9 are always
h-east commented 4 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1619

diff --git a/runtime/doc/version9.txt b/runtime/doc/version9.txt
index 3b719eb9c..0de89574c 100644
--- a/runtime/doc/version9.txt
+++ b/runtime/doc/version9.txt
@@ -41581,7 +41581,7 @@ Changed~
   function |get()-func|
 - |:bwipe| also wipes jumplist and tagstack data
 - moving in the buffer list using |:bnext| and similar commands, behaves as
-  documented and skips help buffers (if not run from a help buffer, else 
+  documented and skips help buffers (if not run from a help buffer, else
   moves to the next/previous help buffer).
 - allow to complete directories from 'cdpath' for |:cd| and similar commands,
   add the "cd_in_path" completion type for e.g. |:command-complete| and
@@ -41610,7 +41610,7 @@ Functions: ~
 Autocommands: ~

 |CursorMovedC|     after the cursor was moved in the comamnd-line
-|KeyInputPre|      process any Key event in any mode
+|KeyInputPre|      before the process any key event in any mode
 |SessionWritePost| after writing the session file |:mksession|
 |TermResponseAll|  after the terminal response to |t_RV| and others is
            received
h-east commented 4 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1614

diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt
index 432a98671..97c084ae2 100644
--- a/runtime/doc/map.txt
+++ b/runtime/doc/map.txt
@@ -1631,13 +1631,13 @@ completion can be enabled:
    -complete=compiler  compilers
    -complete=cscope    |:cscope| suboptions
    -complete=dir       directory names
-   -complete=dir_in_path   directory names in |'cdpath'|
+   -complete=dir_in_path   directory names in 'cdpath'
    -complete=environment   environment variable names
    -complete=event     autocommand events
    -complete=expression    Vim expression
    -complete=file      file and directory names
-   -complete=file_in_path  file and directory names in |'path'|
-   -complete=filetype  filetype names |'filetype'|
+   -complete=file_in_path  file and directory names in 'path'
+   -complete=filetype  filetype names 'filetype'
    -complete=function  function name
    -complete=help      help subjects
    -complete=highlight highlight groups
@@ -1652,7 +1652,7 @@ completion can be enabled:
    -complete=packadd   optional package |pack-add| names
    -complete=shellcmd  Shell command
    -complete=sign      |:sign| suboptions
-   -complete=syntax    syntax file names |'syntax'|
+   -complete=syntax    syntax file names 'syntax'
    -complete=syntime   |:syntime| suboptions
    -complete=tag       tags
    -complete=tag_listfiles tags, file names are shown when CTRL-D is hit

後でまとめてやる。(次コメント参照)

h-east commented 4 months ago

上記、|'～'| の件、

:helpgrep |'\l\+'| @en

すると、79行に存在しているので、この件だけでPR送っても良いかも。

h-east commented 4 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1628

diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index b921cb54a..5019f483c 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -3125,7 +3125,7 @@ text...
                let lconst[1][0] = 'b'  " OK
 <                          *E995*
            It is an error to specify an existing variable with
-           :const. >
+           |:const|. >
                :let x = 1
                :const x = 1  " Error!
 <                          *E996*
h-east commented 4 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1634 - Fix typo

diff --git a/runtime/doc/insert.txt b/runtime/doc/insert.txt
index e85f341c8..8c0c13b47 100644
--- a/runtime/doc/insert.txt
+++ b/runtime/doc/insert.txt
@@ -1185,7 +1185,7 @@ items:
            defaults to an empty string
    hl_group    allows specifying an additional highlight group to
            apply extra attributes to completion items in the
-           popupmenu. Is combined with |hl-PmenuSel| and
+           popupmenu. It is combined with |hl-PmenuSel| and
            |hl-Pmenu| highlighting attributes to apply cterm and
            gui properties, such as strikethrough to the
            completion items.

文章が大幅に変わったので、当該箇所はなくなった。

h-east commented 4 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1634

diff --git a/runtime/doc/insert.txt b/runtime/doc/insert.txt
index e85f341c8..6106eeb2b 100644
--- a/runtime/doc/insert.txt
+++ b/runtime/doc/insert.txt
@@ -2007,7 +2007,7 @@ command in ex mode: >
    two
    .
    :visual
-<appends the following text, after the cursor line: >
+appends the following text, after the cursor line: >
    one
    two
 <
h-east commented 4 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1636

diff --git a/runtime/doc/terminal.txt b/runtime/doc/terminal.txt
index 6f98cba44..ab20ffa8a 100644
--- a/runtime/doc/terminal.txt
+++ b/runtime/doc/terminal.txt
@@ -1253,7 +1253,7 @@ Starting ~
                            *termdebug-starting*
 Load the plugin with this command: >
    packadd termdebug
-<When loading the plugin from the |.vimrc| file, add the "!" attribute: >
+When loading the plugin from the |.vimrc| file, add the "!" attribute: >
    packadd! termdebug
 <                          *:Termdebug*
 To start debugging use `:Termdebug` or `:TermdebugCommand` followed by the
h-east commented 4 months ago

ここまでをPRed。(一部を除く) https://github.com/vim/vim/pull/15371

→ merged

h-east commented 4 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1639

diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 8f8f70a74..d2d673710 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -2260,7 +2260,7 @@ A jump table for the options with a short description can be found at |Q_op|.
                        *'cpoptions'* *'cpo'* *cpo*
 'cpoptions' 'cpo'  string  (Vim default: "aABceFsz",
                 Vi default:  all flags, except "#{|&/\."
-                                 |$VIM_POSIX|:  all flags)
+                |$VIM_POSIX|:  all flags)
            global
    A sequence of single character flags.  When a character is present
    this indicates Vi-compatible behavior.  This is used for things where
h-east commented 3 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1643

diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt
index f2ba03f90..244007d06 100644
--- a/runtime/doc/repeat.txt
+++ b/runtime/doc/repeat.txt
@@ -793,7 +793,8 @@ messages: >
    :echo gettext("Hello", "foobar")
 <
 Where:
-  "Hello"  the message "Hello" to be translated into the user's language |:lang|
+  "Hello"  the message "Hello" to be translated into the user's language
+       |:lang|
   "foobar" the package identifier, which was previously defined using the
        |bindtextdomain()| function.
h-east commented 3 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1653

diff --git a/runtime/doc/autocmd.txt b/runtime/doc/autocmd.txt
index f6d32db39..69aa24f78 100644
--- a/runtime/doc/autocmd.txt
+++ b/runtime/doc/autocmd.txt
@@ -1428,8 +1428,8 @@ WinLeave          Before leaving a window.  If the window to be
 WinNewPre          Before creating a new window. Triggered
                before commands that modify window layout by
                creating a split.
-               Not done for creating tabs or for the first
-               window, as the window structure is not
+               Not done for creating tab page or for the
+               first window, as the window structure is not
                initialized yet and so is generally not safe.
                It is not allowed to modify window layout
                while executing commands for the WinNewPre
h-east commented 3 months ago

PRed. https://github.com/vim/vim/pull/15478

→ merged

h-east commented 3 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1651

diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt
index 8e33d0244..d76748d11 100644
--- a/runtime/doc/syntax.txt
+++ b/runtime/doc/syntax.txt
@@ -2158,7 +2158,7 @@ number is that redrawing can become slow.

 JSON           *json.vim* *ft-json-syntax* *g:vim_json_conceal*
-                          *g:vim_json_warnings*
+                       *g:vim_json_warnings*

 The json syntax file provides syntax highlighting with conceal support by
 default. To disable concealment: >
h-east commented 3 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1668

diff --git a/runtime/doc/insert.txt b/runtime/doc/insert.txt
index 286c6d4c2..a47d2f5f2 100644
--- a/runtime/doc/insert.txt
+++ b/runtime/doc/insert.txt
@@ -1191,9 +1191,10 @@ items:
            to the completion items
    kind_hlgroup    an additional highlight group specifically for setting
            the highlight attributes of the completion kind. When
-           this field is present, it will override the |hl-PmenuKind|
-           highlight group, allowing for the customization of
-           ctermfd and guifg properties for the completion kind
+           this field is present, it will override the
+           |hl-PmenuKind| highlight group, allowing for the
+           customization of ctermfd and guifg properties for the
+           completion kind

 All of these except "icase", "equal", "dup" and "empty" must be a string.  If
 an item does not meet these requirements then an error message is given and

既に修正されている

h-east commented 3 months ago

Vim Script --> Vim script

diff --git a/runtime/syntax/generator/README.md b/runtime/syntax/generator/README.md
index 83acedabe..736237215 100644
--- a/runtime/syntax/generator/README.md
+++ b/runtime/syntax/generator/README.md
@@ -1,6 +1,6 @@
-# Generator of Vim Script Syntax File
+# Generator of Vim script Syntax File

-This directory contains a Vim Script generator, that will parse the Vim source file and
+This directory contains a Vim script generator, that will parse the Vim source file and
 generate a vim.vim syntax file.

 Files in this directory where copied from https://github.com/vim-jp/syntax-vim-ex/
h-east commented 3 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1669

diff --git a/runtime/doc/filetype.txt b/runtime/doc/filetype.txt
index a7ed92880..cbe801ae4 100644
--- a/runtime/doc/filetype.txt
+++ b/runtime/doc/filetype.txt
@@ -754,7 +754,7 @@ Global mapping:

 Local mappings:
 <Plug>ManBS
-<LocalLeader>h Clear backspace <BS> characters from the buffer
+<LocalLeader>h Clear backspace <BS> characters from the buffer.
 CTRL-]     Jump to the manual page for the word under the cursor.
 CTRL-T     Jump back to the previous manual page.
h-east commented 2 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1679

diff --git a/runtime/doc/starting.txt b/runtime/doc/starting.txt
index 02885e6c5..0efba069b 100644
--- a/runtime/doc/starting.txt
+++ b/runtime/doc/starting.txt
@@ -847,7 +847,8 @@ accordingly.  Vim proceeds in this order:
    'compatible' is only done later.  Add a ":set nocp" command if you
    like.  For the Macintosh the $VIMRUNTIME/macmap.vim is read.

-     *VIMINIT* *.vimrc* *_vimrc* *EXINIT* *.exrc* *_exrc* *$MYVIMRC* *$MYVIMDIR*
+           *VIMINIT* *.vimrc* *_vimrc* *EXINIT* *.exrc* *_exrc*
+           *$MYVIMRC* *$MYVIMDIR*
      c. Five places are searched for initializations.  The first that exists
    is used, the others are ignored.  The $MYVIMRC environment variable is
    set to the file that was first found, unless $MYVIMRC was already set
@@ -972,9 +973,9 @@ accordingly.  Vim proceeds in this order:
    The |v:vim_did_enter| variable is set to 1.
    The |VimEnter| autocommands are executed.

-The $MYVIMRC or $MYGVIMRC file will be set to the first found vimrc and/or
-gvimrc file while $MYVIMDIR is set to the users personal runtime directory
-'rtp' (typically the first entry in 'runtimepath').
+The $MYVIMRC or $MYGVIMRC environment variable will be set to the first found
+vimrc and/or gvimrc file while $MYVIMDIR is set to the users personal runtime
+directory 'rtp' (typically the first entry in 'runtimepath').

 Some hints on using initializations ~
h-east commented 2 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1685

diff --git a/runtime/doc/pi_getscript.txt b/runtime/doc/pi_getscript.txt
index 7d1781198..9c34471a5 100644
--- a/runtime/doc/pi_getscript.txt
+++ b/runtime/doc/pi_getscript.txt
@@ -281,14 +281,14 @@ With :AutoInstall: enabled, as it is by default, files which end with

    ---.tar.bz2  : decompressed & untarred in .vim/ directory
    ---.vba.bz2  : decompressed in .vim/ directory, then vimball handles it
-   ---.vmb.bz2  : decompressed in .vim/ directory, then vimball handles it
+   ---.vmb.bz2  : idem
    ---.vim.bz2  : decompressed & moved into .vim/plugin directory
    ---.tar.gz   : decompressed & untarred in .vim/ directory
    ---.vba.gz   : decompressed in .vim/ directory, then vimball handles it
-   ---.vmb.gz   : decompressed in .vim/ directory, then vimball handles it
+   ---.vmb.gz   : idem
    ---.vim.gz   : decompressed & moved into .vim/plugin directory
    ---.vba      : moved to .vim/ directory, then vimball handles it
-   ---.vmb      : moved to .vim/ directory, then vimball handles it
+   ---.vmb      : idem
    ---.vim      : moved to .vim/plugin directory
    ---.zip      : unzipped in .vim/ directory
h-east commented 2 months ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1696

diff --git a/runtime/doc/version9.txt b/runtime/doc/version9.txt
index 94e662d6d..bc4561c29 100644
--- a/runtime/doc/version9.txt
+++ b/runtime/doc/version9.txt
@@ -41608,7 +41608,7 @@ Functions: ~
 |diff()|       diff two Lists of strings
 |filecopy()|       copy a file {from} to {to}
 |foreach()|        apply function to List items
-|getcmdprompt()|        get prompt for input()/confirm()
+|getcmdprompt()|   get prompt for input()/confirm()
 |getregion()|      get a region of text from a buffer
 |getregionpos()|   get a list of positions for a region
 |id()|         get unique identifier for a Dict, List, Object,
mikoto2000 commented 2 months ago

Vim version: 9.1.678

user_xx を一通り見ていたら長くなったので、折り畳み+diffファイル添付します

diff ```diff diff --git a/runtime/doc/usr_02.txt b/runtime/doc/usr_02.txt index 486426ed7..37be401d1 100644 --- a/runtime/doc/usr_02.txt +++ b/runtime/doc/usr_02.txt @@ -32,7 +32,7 @@ To start Vim, enter this command: > In UNIX you can type this at any command prompt. If you are running Microsoft Windows, open a Command Prompt and enter the command. In either case, Vim starts editing a file called file.txt. Because this -is a new file, you get a blank window. This is what your screen will look +is a new file, you get a blank window. This is what your screen will look like: +---------------------------------------+ @@ -322,7 +322,7 @@ the "a" (append) command. to and that's not saying much for the turtle!!! ~ -move the cursor over to the dot at the end of the line. Then type "x" to +move the cursor over to the dot at the end of the line. Then type "x" to delete the period. The cursor is now positioned at the end of the line on the e in turtle. Now type > @@ -535,7 +535,7 @@ Summary: *help-summary* > < And for the 'guioptions' flags: > :help go- -4) Normal mode commands do not have a prefix. To go to the help page for the +4) Normal mode commands do not have a prefix. To go to the help page for the "gt" command: > :help gt @@ -585,7 +585,7 @@ Summary: *help-summary* > at: > :help pattern.txt -12) Registers always start with "quote". To find out about the special ":" +12) Registers always start with "quote". To find out about the special ":" register: > :help quote: @@ -604,7 +604,7 @@ Summary: *help-summary* > < talks about the append Vim script function rather than how to append text in the current buffer. -14) Mappings are talked about in the help page :h |map.txt|. Use > +14) Mappings are talked about in the help page :h |map.txt|. Use > :help mapmode-i < to find out about the |:imap| command. Also use :map-topic to find out about certain subtopics particular for mappings. e.g: > @@ -640,7 +640,7 @@ Summary: *help-summary* > friendly way. Start at |usr_toc.txt| to find the table of content (as you might have guessed): > :help usr_toc.txt -< Skim over the contents to find interesting topics. The "Digraphs" and +< Skim over the contents to find interesting topics. The "Digraphs" and "Entering special characters" items are in chapter 24, so to go to that particular help page: > :help usr_24.txt diff --git a/runtime/doc/usr_05.txt b/runtime/doc/usr_05.txt index 21629e3ca..421e21329 100644 --- a/runtime/doc/usr_05.txt +++ b/runtime/doc/usr_05.txt @@ -446,7 +446,7 @@ This way you can use the plugin with the default key bindings `gc` and similar for commenting (which is a well-established mapping in the Vim community). If you add this line to your vimrc file, then you need to restart Vim to have -the package loaded. Once the package is loaded, read about it at: > +the package loaded. Once the package is loaded, read about it at: > :h comment.txt diff --git a/runtime/doc/usr_06.txt b/runtime/doc/usr_06.txt index 6d76c53e1..3d9e17f7d 100644 --- a/runtime/doc/usr_06.txt +++ b/runtime/doc/usr_06.txt @@ -184,7 +184,7 @@ this command: > :runtime syntax/colortest.vim You will see text in various color combinations. You can check which ones are -readable and look nice. These aren't the only colors available to you though. +readable and look nice. These aren't the only colors available to you though. You can specify #rrggbb hex colors and you can define new names for hex colors in |v:colornames| like so: > @@ -196,7 +196,7 @@ to define these colors only when they do not exist: > call extend(v:colornames, {'mine_red': '#aa0000'}, 'keep') This allows users of the color scheme to override the precise definition of -that color prior to loading your color scheme. For example, in a |.vimrc| +that color prior to loading your color scheme. For example, in a |.vimrc| file: > runtime colors/lists/css_colors.vim @@ -204,7 +204,7 @@ file: > colorscheme yourscheme As a color scheme author, you should be able to rely on some color names for -GUI colors. These are defined in `colors/lists/default.vim`. All such files +GUI colors. These are defined in `colors/lists/default.vim`. All such files found on the |'runtimepath'| are loaded each time the colorscheme command is run. A canonical list is provided by the vim distribution, which should include all X11 colors (previously defined in rgb.txt). diff --git a/runtime/doc/usr_07.txt b/runtime/doc/usr_07.txt index ea4875ec5..a433a7759 100644 --- a/runtime/doc/usr_07.txt +++ b/runtime/doc/usr_07.txt @@ -219,8 +219,8 @@ Suppose you are editing the file "one.txt". Somewhere halfway through the file you use "x" to delete a character. Then you go to the last line with "G" and write the file with ":w". You edit several other files, and then use ":edit one.txt" to come back to "one.txt". If you now use `" Vim jumps to the -last line of the file. Using `. takes you to the position where you deleted -the character. Even when you move around in the file `" and `. will take you +last line of the file. Using `. takes you to the position where you deleted +the character. Even when you move around in the file `" and `. will take you to the remembered position. At least until you make another change or leave the file. diff --git a/runtime/doc/usr_22.txt b/runtime/doc/usr_22.txt index 57862edaa..94e0adf5c 100644 --- a/runtime/doc/usr_22.txt +++ b/runtime/doc/usr_22.txt @@ -214,11 +214,11 @@ directory, it will go back to using the shared directory. TAB LOCAL DIRECTORY When you open a new tab page, it uses the directory of the window in the -previous tab page from which the new tab page was opened. You can change the -directory of the current tab page using the `:tcd` command. All the windows in +previous tab page from which the new tab page was opened. You can change the +directory of the current tab page using the `:tcd` command. All the windows in a tab page share this directory except for windows with a window-local -directory. Any new windows opened in this tab page will use this directory as -the current working directory. Using a `:cd` command in a tab page will not +directory. Any new windows opened in this tab page will use this directory as +the current working directory. Using a `:cd` command in a tab page will not change the working directory of tab pages which have a tab local directory. When the global working directory is changed using the `:cd` command in a tab page, it will also change the current tab page working directory. diff --git a/runtime/doc/usr_41.txt b/runtime/doc/usr_41.txt index 27df85ac7..7efe4a883 100644 --- a/runtime/doc/usr_41.txt +++ b/runtime/doc/usr_41.txt @@ -30,13 +30,13 @@ Table of contents: |usr_toc.txt| *41.1* Introduction *vim-script-intro* *script* Let's start with some nomenclature. A Vim script is any file that Vim can -interpret and execute. This includes files written in Vim's scripting language +interpret and execute. This includes files written in Vim's scripting language like for example .vim files or configuration files like .vimrc and .gvimrc. These scripts may define functions, commands and settings that Vim uses to customize and extend its behavior. With a slight abuse of nomenclature, we will use "Vim script" to refer to the -Vim scripting language throughout this documentation. This shorthand helps to +Vim scripting language throughout this documentation. This shorthand helps to streamline explanations and discussions about scripting with Vim. A Vim plugin is a collection of one or more Vim scripts, along with additional @@ -1384,7 +1384,7 @@ Various: *various-functions* mode() get current editing mode state() get current busy state visualmode() last visual mode used - exists() check if a variable, function, etc. exists + exists() check if a variable, function, etc. exists exists_compiled() like exists() but check at compile time has() check if a feature is supported in Vim changenr() return number of most recent change diff --git a/runtime/doc/usr_43.txt b/runtime/doc/usr_43.txt index 41b08de18..b2d265cfe 100644 --- a/runtime/doc/usr_43.txt +++ b/runtime/doc/usr_43.txt @@ -63,7 +63,7 @@ buffer. This works with any mapping command: ":map!", ":vmap", etc. The The line to set b:undo_ftplugin is for when the filetype is set to another value. In that case you will want to undo your preferences. The -b:undo_ftplugin variable is executed as a command. Watch out for characters +b:undo_ftplugin variable is executed as a command. Watch out for characters with a special meaning inside a string, such as a backslash. You can find examples for filetype plugins in this directory: > diff --git a/runtime/doc/usr_90.txt b/runtime/doc/usr_90.txt index 418f1f0dc..59529cc8d 100644 --- a/runtime/doc/usr_90.txt +++ b/runtime/doc/usr_90.txt @@ -308,7 +308,7 @@ MS-WINDOWS Upgrading is mostly equal to installing a new version. Just unpack the files in the same place as the previous version. A new directory will be created, e.g., "vim82", for the files of the new version. Your runtime files, vimrc -file, viminfo, etc. will be left alone. +file, viminfo, etc. will be left alone. If you want to run the new version next to the old one, you will have to do some handwork. Don't run the install program, it will overwrite a few files of the old version. Execute the new binaries by specifying the full path. ```

diff.patch

h-east commented 1 month ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1710

diff --git a/runtime/doc/usr_toc.txt b/runtime/doc/usr_toc.txt
index c70c945cf..d0622a86e 100644
--- a/runtime/doc/usr_toc.txt
+++ b/runtime/doc/usr_toc.txt
@@ -2,7 +2,7 @@

             VIM USER MANUAL - by Bram Moolenaar

-                 Table Of Contents            *user-manual* *usr*
+                 Table Of Contents     *user-manual* *usr*

 ==============================================================================
 Overview ~
h-east commented 1 month ago

PRed. https://github.com/vim/vim/pull/15801 https://github.com/vim/vim/pull/15802

→ merged

h-east commented 1 month ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1730

diff --git a/runtime/doc/undo.txt b/runtime/doc/undo.txt
index 7a83e776e..74923aac5 100644
--- a/runtime/doc/undo.txt
+++ b/runtime/doc/undo.txt
@@ -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
            times.
                            *: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}m      Go to newer text state about {N} minutes later.
 :lat[er] {N}h      Go to newer text state about {N} hours later.
mityu commented 1 month ago 
diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt
index 15de27db5..8f872b4fd 100644
--- a/runtime/doc/builtin.txt
+++ b/runtime/doc/builtin.txt
@@ -5202,7 +5202,7 @@ glob({expr} [, {nosuf} [, {list} [, {alllinks}]]])        *glob()*
        on {list}

-glob2regpat({string})                   *glob2regpat()*
+glob2regpat({string})                  *glob2regpat()*
        Convert a file pattern, as used by glob(), into a search
        pattern.  The result can be used to match with a string that
        is a file name.  E.g. >
@@ -5655,7 +5655,7 @@ iconv({string}, {from}, {to})             *iconv()*
        Return type: |String|

-id({item})                             *id()*
+id({item})                         *id()*
        The result is a unique String associated with the {item} and
        not with the {item}'s contents. It is only valid while the
        {item} exists and is referenced. It is valid only in the
@@ -7080,7 +7080,7 @@ matchbufline({buf}, {pat}, {lnum}, {end}, [, {dict}])
        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()|
        or one of the |:match| commands.  Returns 0 if successful,
        otherwise -1.  See example for |matchadd()|.  All matches can
h-east commented 1 month ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1748

diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt
index 1c66042cc..654b048d9 100644
--- a/runtime/doc/syntax.txt
+++ b/runtime/doc/syntax.txt
@@ -1679,20 +1679,20 @@ on" command in your .vimrc file.
 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
 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
-determine which source form has been used by examining the file extension
-using conventions common to the ifort, gfortran, Cray, NAG, and PathScale
-compilers (.f, .for, .f77 for fixed-source, .f90, .f95, .f03, .f08 for
-free-source). No default is used for the .fpp and .ftn file extensions because
-different compilers treat them differently. If none of this works, then the
-script examines the first five columns of the first 500 lines of your file. If
-no signs of free source form are detected, then the file is assumed to be in
-fixed source form.  The algorithm should work in the vast majority of cases.
-In some cases, such as a file that begins with 500 or more full-line comments,
-the script may incorrectly decide that the code is in fixed form.  If that
-happens, just add a non-comment statement beginning anywhere in the first five
-columns of the first twenty-five lines, save (:w), and then reload (:e!) the
-file.
+neither of these variables have been set. In that case, the syntax script
+attempts to determine which source form has been used by examining the file
+extension using conventions common to the ifort, gfortran, Cray, NAG, and
+PathScale compilers (.f, .for, .f77 for fixed-source, .f90, .f95, .f03, .f08
+for free-source).  No default is used for the .fpp and .ftn file extensions
+because different compilers treat them differently. If none of this works,
+then the script examines the first five columns of the first 500 lines of your
+file. If no signs of free source form are detected, then the file is assumed
+to be in fixed source form.  The algorithm should work in the vast majority of
+cases.  In some cases, such as a file that begins with 500 or more full-line
+comments, the script may incorrectly decide that the code is in fixed form.
+If that happens, just add a non-comment statement beginning anywhere in the
+first five columns of the first twenty-five lines, save (:w), and then reload
+(:e!) the file.

 Vendor extensions ~
 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*
                        *b:lf_shell_syntax*

-For the lf file manager configuration files (lfrc) the shell commands
-syntax highlighting can be changed globally and per buffer by setting
-a different 'include' command search pattern using these variables:
+For the lf file manager configuration files (lfrc) the shell commands syntax
+highlighting can be changed globally and per buffer by setting a different
+'include' command search pattern using these variables: >
    let g:lf_shell_syntax = "syntax/dosbatch.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

-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

@@ -2710,9 +2711,9 @@ specified. Default = 1 >

    :let g:pandoc#syntax#codeblocks#embeds#use = 1

-For specify what languages and using what syntax files to highlight embeds. This is a
-list of language names. When the language pandoc and vim use don't match, you
-can use the "PANDOC=VIM" syntax. For example: >
+For specify what languages and using what syntax files to highlight embeds.
+This is a list of language names. When the language pandoc and vim use don't
+match, you can use the "PANDOC=VIM" syntax. For example: >

    :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
 <
 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.

@@ -5718,8 +5719,8 @@ guisp={color-name}                    *highlight-guisp*
        :highlight Comment guifg=#11f0c3 guibg=#ff00ff
 <
    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|.
-   For example: >
+   repeatedly, you can define a (lower case) name for it in
+   |v:colornames|.  For example: >

        # provide a default value for this color but allow the user to
        # override it.
h-east commented 1 month ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1759

diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt
index 496093d11..a23d4bf42 100644
--- a/runtime/doc/syntax.txt
+++ b/runtime/doc/syntax.txt
@@ -5309,9 +5309,9 @@ of colors by using the `:colorscheme` command, for example: >
            This is basically the same as >
                :echo g:colors_name
 <          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
-           legacy versions of peachpuff and desert. When compiled
+           legacy versions of peachpuff and desert.  When compiled
            without the |+eval| feature it will output "unknown".

 :colo[rscheme] {name}  Load color scheme {name}.  This searches 'runtimepath'
h-east commented 1 month ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1762

diff --git a/runtime/doc/filetype.txt b/runtime/doc/filetype.txt
index be3ba021d..67905bc19 100644
--- a/runtime/doc/filetype.txt
+++ b/runtime/doc/filetype.txt
@@ -946,8 +946,8 @@ To enable: >
    let g:typst_folding = 1
 <
                            *g:typst_foldnested*
-When |TRUE| the Typst filetype plugin will fold nested heading under their parents
-(default: |TRUE|)
+When |TRUE| the Typst filetype plugin will fold nested heading under their
+parents. (default: |TRUE|)

 To disable: >
    let g:typst_foldnested = 0
h-east commented 1 month ago

行末に余計なスペース

diff --git a/runtime/defaults.vim b/runtime/defaults.vim
index 459841ffc..c5be52660 100644
--- a/runtime/defaults.vim
+++ b/runtime/defaults.vim
@@ -115,7 +115,7 @@ if 1
       \ |   execute "normal! g`\""
       \ | 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
     " makes syntax highlighting often hard to read with bg=light
     " undo this using:  ":au! vimStartup TermResponse"
h-east commented 1 month ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1773

- サンプルコードがハイライトされていない。(要ネスト)

diff ```patch diff --git a/runtime/doc/pi_netrw.txt b/runtime/doc/pi_netrw.txt index a9564374f..3467df6c1 100644 --- a/runtime/doc/pi_netrw.txt +++ b/runtime/doc/pi_netrw.txt @@ -1495,34 +1495,34 @@ The function should return the URL or file name to be used by gx, and will fall back to the default behavior if it returns an empty string. For example, special handlers for links Markdown and HTML are > -" make gx work on concealed links regardless of exact cursor position -function Netrw_get_URL_markdown() - " markdown URL such as [link text](http://ya.ru 'yandex search') - try - let save_view = winsaveview() - if searchpair('\[.\{-}\](', '', ')\zs', 'cbW', '', line('.')) > 0 - return matchstr(getline('.')[col('.')-1:], '\[.\{-}\](\zs' .. g:netrw_regex_url .. '\ze\(\s\+.\{-}\)\?)') - endif - finally - call winrestview(save_view) - return '' - endtry -endfunction - -function Netrw_get_URL_html() - " HTML URL such as Python is here - " - try - let save_view = winsaveview() - if searchpair('\|/>\)\zs', 'cbW', '', line('.')) > 0 - return matchstr(getline('.')[col('.') - 1 : ], - \ 'href=["'.."'"..']\?\zs\S\{-}\ze["'.."'"..']\?/\?>') - endif - finally - call winrestview(save_view) - return '' - endtry -endfunction + " make gx work on concealed links regardless of exact cursor position + function Netrw_get_URL_markdown() + " markdown URL such as [link text](http://ya.ru 'yandex search') + try + let save_view = winsaveview() + if searchpair('\[.\{-}\](', '', ')\zs', 'cbW', '', line('.')) > 0 + return matchstr(getline('.')[col('.')-1:], '\[.\{-}\](\zs' .. g:netrw_regex_url .. '\ze\(\s\+.\{-}\)\?)') + endif + finally + call winrestview(save_view) + return '' + endtry + endfunction + + function Netrw_get_URL_html() + " HTML URL such as Python is here + " + try + let save_view = winsaveview() + if searchpair('\|/>\)\zs', 'cbW', '', line('.')) > 0 + return matchstr(getline('.')[col('.') - 1 : ], + \ 'href=["'.."'"..']\?\zs\S\{-}\ze["'.."'"..']\?/\?>') + endif + finally + call winrestview(save_view) + return '' + endtry + endfunction < Other than a file path, the text under the cursor may be a URL. Netrw uses ```

(2024-11-02) よしなに修正されてた。

mikoto2000 commented 1 month ago

Vim version: 9.1.818

pattern.txt をひと通り見ていたら長くなったので、折り畳み+diffファイル添付します

diff ```diff diff --git a/runtime/doc/pattern.txt b/runtime/doc/pattern.txt index 4351944df..da5338a55 100644 --- a/runtime/doc/pattern.txt +++ b/runtime/doc/pattern.txt @@ -757,7 +757,7 @@ overview. \([a-z]\+\)\zs,\1 ",abc" in "abc,abc" \@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 slow. Example, check if there is a "<" just before "span": /<\@1<=span @@ -783,7 +783,7 @@ overview. \(\/\/.*\)\@ /\%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 < would match "foo bar" if the Visual selection continues after the "r". 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 cursor is): > /\%>.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: > /^.*\%17v. < 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'. - If two characters in the sequence are separated by '-', this is shorthand for the full list of ASCII characters between them. E.g., - "[0-9]" matches any decimal digit. If the starting character exceeds - the ending character, e.g. [c-a], E944 occurs. Non-ASCII characters + "[0-9]" matches any decimal digit. If the starting character exceeds + 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 - in the old regexp engine. For example, searching by [\u3000-\u4000] - after setting re=1 emits a E945 error. Prepending \%#=2 will fix it. + in the old regexp engine. For example, searching by [\u3000-\u4000] + after setting re=1 emits a E945 error. Prepending \%#=2 will fix it. - A character class expression is evaluated to the set of characters belonging to that character class. The following character classes are supported: @@ -1444,7 +1444,7 @@ Finally, these constructs are unique to Perl: display you may get unexpected results. That is because Vim 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| command. The latter returns a list with highlight groups and patterns defined by both |matchadd()| and |:match|. @@ -1480,7 +1480,7 @@ Finally, these constructs are unique to Perl: with the lowest number has priority if several match at the same position. It uses the match id 3. 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 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 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 -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 +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 present in any order in a string. 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. 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 -matching strings. The matchfuzzypos() functions returns the List of matches, +a string in a List of strings. The matchfuzzy() function returns a List of +matching strings. The matchfuzzypos() functions returns the List of matches, the matching positions and the fuzzy match scores. The "f" flag of `:vimgrep` enables fuzzy matching. ```

diff.patch

h-east commented 3 weeks ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1773

diff --git a/runtime/doc/pi_netrw.txt b/runtime/doc/pi_netrw.txt
index dc95a5405..e9f282f60 100644
--- a/runtime/doc/pi_netrw.txt
+++ b/runtime/doc/pi_netrw.txt
@@ -1537,7 +1537,7 @@ Associated setting variables:
    |g:netrw_nogx|  prevent gx map while editing
    |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:
h-east commented 2 weeks ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1782

diff --git a/runtime/doc/pi_tutor.txt b/runtime/doc/pi_tutor.txt
index 0f8479e88..35f17a974 100644
--- a/runtime/doc/pi_tutor.txt
+++ b/runtime/doc/pi_tutor.txt
@@ -3,24 +3,24 @@
 INTERACTIVE TUTORIALS FOR VIM           *vim-tutor-mode*

 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*

 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
 by double-clicking them.

 1.1 Commands
 ------------
                                      *: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
            '.tutor' files found in the 'tutor/'  folder in
-           the 'runtimepath'. Tutorials prefixed with 'vim-' will
-           always be shown first.
+           the 'runtimepath'.  Tutorials prefixed with 'vim-'
+           will always be shown first.

            If no {tutorial} is provided, the command starts the
            'vim-01-beginner' tutorial, which is equivalent to
@@ -29,7 +29,7 @@ by double-clicking them.
 =============================================================================
 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: >

     :Tutor tutor
h-east commented 2 weeks ago

- TOC に pi_tutor.txt がない。

diff --git a/runtime/doc/help.txt b/runtime/doc/help.txt
index faa5f3271..446a9ce3b 100644
--- a/runtime/doc/help.txt
+++ b/runtime/doc/help.txt
@@ -232,6 +232,7 @@ Standard plugins ~
 |pi_paren.txt|     Highlight matching parens
 |pi_spec.txt|      Filetype plugin to work with rpm spec files
 |pi_tar.txt|       Tar file explorer
+|pi_tutor.txt|     Interactive tutorials for Vim
 |pi_vimball.txt|   Create a self-installing Vim script
 |pi_zip.txt|       Zip archive explorer

(2024-11-07) これだけ先にPRした。 → Fixed.

h-east commented 2 weeks ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1787

diff --git a/runtime/doc/if_pyth.txt b/runtime/doc/if_pyth.txt
index 0b6140f25..9101ba531 100644
--- a/runtime/doc/if_pyth.txt
+++ b/runtime/doc/if_pyth.txt
@@ -201,7 +201,7 @@ vim.eval(str)                       *python-eval*
    [{'cmd': '/^eval_expr(arg, nextcmd)$/', 'static': 0, 'name': ~
    '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,
    use the {locals} dict when calling |py3eval()| and friends.
h-east commented 2 weeks ago

PRed. https://github.com/vim/vim/pull/16021

→ merged

h-east commented 1 week ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1822#discussion_r1843288248

diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt
index ab6368198..1f029fc92 100644
--- a/runtime/doc/builtin.txt
+++ b/runtime/doc/builtin.txt
@@ -3789,7 +3789,7 @@ getbufvar({buf}, {varname} [, {def}])             *getbufvar()*

 getcellpixels()                        *getcellpixels()*
        Returns a |List| of terminal cell pixel size.
-       List format is [xpixels, ypixels].
+       List format is [xpixel, ypixel].
        Only works on (terminal) Unix.  For gVim, on other systems and
        on failure returns [].
h-east commented 5 days ago

From https://github.com/vim-jp/vimdoc-ja-working/pull/1839#discussion_r1849754952

diff --git a/runtime/doc/terminal.txt b/runtime/doc/terminal.txt
index 593dec77c..258421693 100644
--- a/runtime/doc/terminal.txt
+++ b/runtime/doc/terminal.txt
@@ -1746,8 +1746,8 @@ mechanisms like `echo` statements (or similar) to help you in your job.
 For this reason, you can set: >
     let g:termdebug_config['debug'] = true
 <
-This sets the `DEBUG` variable to `true` in the source code that you can use
-within the source code. An example of its usage follows: >
+This sets the `DEBUG` variable to `true`, which can be referenced in the
+source code.  An example of its usage follows: >
     if exists('g:termdebug_loaded')
       if DEBUG
    Echoerr('Termdebug already loaded.')