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

[h-east]

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

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

関連: #1172, #1321, #1387

[h-east]

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]

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]

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]

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

• 1行に収まる。
• ピリオドの後は2スペース。

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]

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

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]

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]

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]

上記、|'～'| の件、

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

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

[h-east]

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]

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]

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]

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]

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

→ merged

[h-east]

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]

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

• 80桁超え

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]

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

• tabs --> tab page

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]

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

→ merged

[h-east]

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

• space to tab

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]

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

• 80桁超え

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]

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]

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]

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

• 80桁超え
• $～ は file じゃない。。

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]

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

• 前行と同じ場合は idem を使用した方が読み手にも優しいと思う。(既に多数使われている)

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]

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]

Vim version: 9.1.678

• ピリオドの後は 2 スペース

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