vim-jp / issues

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

本家helpのtypo報告スレ (Vim 8.2) #1321

Closed h-east closed 2 years ago

h-east commented 4 years ago

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

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

関連: #1172

tsuyoshicho commented 4 years ago

直した版のdiffを再度添付します Vim 8.2.0002 で確認

diff --git a/en/os_win32.txt b/en/os_win32.txt
index 194abfad..7c832fb7 100644
--- a/en/os_win32.txt
+++ b/en/os_win32.txt
@@ -230,7 +230,7 @@ A. VisionFS can't handle certain dot (.) three letter extension file names.
    SCO declares this behavior required for backwards compatibility with 16bit
    DOS/Windows environments.  The two commands below demonstrate the behavior:
 >
-   echo Hello > file.bat~ 
+   echo Hello > file.bat~
    dir > file.bat
 <
    The result is that the "dir" command updates the "file.bat~" file, instead
diff --git a/en/usr_08.txt b/en/usr_08.txt
index 1f8776a1..0947b364 100644
--- a/en/usr_08.txt
+++ b/en/usr_08.txt
@@ -402,7 +402,7 @@ Another way to start in diff mode can be done from inside Vim.  Edit the
 "main.c" file, then make a split and show the differences: >

    :edit main.c
-   :vertical diffsplit main.c~ 
+   :vertical diffsplit main.c~

 The ":vertical" command is used to make the window split vertically.  If you
 omit this, you will get a horizontal split.
diff --git a/en/usr_10.txt b/en/usr_10.txt
index d551d119..ca015205 100644
--- a/en/usr_10.txt
+++ b/en/usr_10.txt
@@ -686,7 +686,7 @@ with any motion command, with text objects and in Visual mode.
 lowercase.  This can be shortened to "guu".  "gUgU" is shortened to "gUU" and
 "g~g~" to "g~~".  Example: >

-               g~~ 
+               g~~
 <  Some GIRLS have Fun    ---->   sOME girls HAVE fUN ~

 ==============================================================================
diff --git a/en/usr_22.txt b/en/usr_22.txt
index 3fcdf31e..4f492f2d 100644
--- a/en/usr_22.txt
+++ b/en/usr_22.txt
@@ -74,9 +74,9 @@ higher.  Pressing "-" does the same thing, without the need to move to the
 You can press <F1> to get help on the things you can do in the netrw file
 browser.  This is what you get: >

-    9. Directory Browsing   netrw-browse   netrw-dir   netrw-list   netrw-help 
+    9. Directory Browsing   netrw-browse   netrw-dir   netrw-list   netrw-help

-    MAPS                                netrw-maps 
+    MAPS                                netrw-maps
         <F1>.............Help.......................................|netrw-help|
         <cr>.............Browsing...................................|netrw-cr|
         <del>............Deleting Files or Directories..............|netrw-delete|
k-takata commented 4 years ago
--- a/runtime/doc/terminal.txt
+++ b/runtime/doc/terminal.txt
@@ -120,7 +120,7 @@ break (cursor keys start with an Esc, so
 You can also create menus similar to terminal mode mappings, but you have to
 use |:tlmenu| instead of |:tmenu|.

-<                          *options-in-terminal*
+                           *options-in-terminal*
 After opening the terminal window and setting 'buftype' to "terminal" the
 TerminalOpen autocommand event is triggered.  This makes it possible to set
 options specifically for the window and buffer.  Example: >
h-east commented 4 years ago

from vim-jp/vimdoc-ja-working/pull/790 括弧の開き/閉じがあっていないのを修正。 (本家も修正が必要な分をこちらに張り付けました)

diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index 62a73048b..62abb177d 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -2640,7 +2640,7 @@ prop_clear({lnum} [, {lnum-end} [, {props}]])
                none    remove all text properties
 prop_find({props} [, {direction}])
                Dict    search for a text property
-prop_list({lnum} [, {props})   List    text properties in {lnum}
+prop_list({lnum} [, {props}])  List    text properties in {lnum}
 prop_remove({props} [, {lnum} [, {lnum-end}]])
                Number  remove a text property
 prop_type_add({name}, {props}) none    define a new property type
@@ -2648,7 +2648,7 @@ prop_type_change({name}, {props})
                none    change an existing property type
 prop_type_delete({name} [, {props}])
                none    delete a property type
-prop_type_get([{name} [, {props}])
+prop_type_get([{name} [, {props}]])
                Dict    get property type values
 prop_type_list([{props}])  List    get list of property types
 pum_getpos()           Dict    position and size of pum if visible
@@ -3041,7 +3041,7 @@ arglistid([{winnr} [, {tabnr}]])
        {winnr} can be the window number or the |window-ID|.

                            *argv()*
-argv([{nr} [, {winid}])
+argv([{nr} [, {winid}]])
        The result is the {nr}th file in the argument list.  See
        |arglist|.  "argv(0)" is the first one.  Example: >
    :let i = 0
diff --git a/runtime/doc/textprop.txt b/runtime/doc/textprop.txt
index 2c6674f05..7a22a890a 100644
--- a/runtime/doc/textprop.txt
+++ b/runtime/doc/textprop.txt
@@ -101,7 +101,7 @@ Manipulating text property types:
 prop_type_add({name}, {props})     define a new property type
 prop_type_change({name}, {props})  change an existing property type
 prop_type_delete({name} [, {props}])   delete a property type
-prop_type_get([{name} [, {props}]) get property type values
+prop_type_get([{name} [, {props}]])    get property type values
 prop_type_list([{props}])      get list of property types

@@ -111,7 +111,7 @@ prop_add({lnum}, {col}, {props})    add a text property
 prop_clear({lnum} [, {lnum-end} [, {bufnr}]])
                    remove all text properties
 prop_find({props} [, {direction}]) search for a text property
-prop_list({lnum} [, {props})       text properties in {lnum}
+prop_list({lnum} [, {props}])          text properties in {lnum}
 prop_remove({props} [, {lnum} [, {lnum-end}]])
                    remove a text property

@@ -289,7 +289,7 @@ prop_type_delete({name} [, {props}])            *prop_type_delete()*
        Can also be used as a |method|: >
            GetPropName()->prop_type_delete()

-prop_type_get([{name} [, {props}])         *prop_type_get()*
+prop_type_get([{name} [, {props}]])            *prop_type_get()*
        Returns the properties of property type {name}.  This is a
        dictionary with the same fields as was given to
        prop_type_add().
tennashi commented 4 years ago

関数名の typo(vim 8.2.285)

diff --git a/en/eval.txt b/en/eval.txt
index 62a73048..01992451 100644
--- a/en/eval.txt
+++ b/en/eval.txt
@@ -2900,7 +2900,7 @@ win_id2win({expr})                Number  get window nr from window ID
 win_screenpos({nr})            List    get screen position of window {nr}
 win_splitmove({nr}, {target} [, {options}])
                                Number  move window {nr} to split of {target}
-win_type([{nr}])               String  type of window {nr}
+win_gettype([{nr}])            String  type of window {nr}
 winbufnr({nr})                 Number  buffer number of window {nr}
 wincol()                       Number  window column of the cursor
 winheight({nr})                        Number  height of window {nr}
tsuyoshicho commented 4 years ago

(patch 8.2.0326 時点)

diff --git a/runtime/doc/os_haiku.txt b/runtime/doc/os_haiku.txt
index 1154ea7..232c49f 100644
--- a/runtime/doc/os_haiku.txt
+++ b/runtime/doc/os_haiku.txt
@@ -25,8 +25,9 @@ targets personal computing.
  9. The meta key modifier  |haiku-meta|
 10. Mouse key mappings     |haiku-mouse|
 11. Color names            |haiku-colors|
-12. Credits            |haiku-support-credits|
-13. Bugs & things To Do        |haiku-bugs|
+12. GUI Toolbar Images         |haiku-toolbar-images|
+13. Credits            |haiku-support-credits|
+14. Bugs & things To Do        |haiku-bugs|

 1. General                     *haiku-general*
h-east commented 4 years ago

コードブロックの閉じカッコ(必要ですよね?)

空行でリセットされるので必ず必要というわけではないです。

k-takata commented 4 years ago

空行ではなくて、行頭が空白文字以外でリセットですね。

tsuyoshicho commented 4 years ago

なるほど、そのフォーマットには合致しているので、除外ということで

k-takata commented 4 years ago

アルファベット順

--- a/runtime/doc/help.txt
+++ b/runtime/doc/help.txt
@@ -198,13 +198,13 @@ Remarks about specific systems ~
 |os_amiga.txt| Amiga
 |os_beos.txt|  BeOS and BeBox
 |os_dos.txt|   MS-DOS and MS-Windows common items
+|os_haiku.txt| Haiku
 |os_mac.txt|   Macintosh
 |os_mint.txt|  Atari MiNT
 |os_msdos.txt| MS-DOS (plain DOS and DOS box under Windows)
 |os_os2.txt|   OS/2
 |os_qnx.txt|   QNX
 |os_risc.txt|  RISC-OS
-|os_haiku.txt| Haiku
 |os_unix.txt|  Unix
 |os_vms.txt|   VMS
 |os_win32.txt| MS-Windows
k-takata commented 4 years ago
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -5837,7 +5837,7 @@ has({feature})    The result is a Number, w
        Also see |exists()|.
        Note that to skip code that has a syntax error when the
        feature is not available, Vim may skip the rest of the line
-       and miss a following `endif`.  Therfore put the `endif` on a
+       and miss a following `endif`.  Therefore put the `endif` on a
        separate line: >
            if has('feature')
              let x = this->breaks->without->the->feature
k-takata commented 4 years ago

https://github.com/vim-jp/issues/issues/1321#issuecomment-566072302

- :unmap ,ab 
+ :unmap ,ab

文章を読めばわかりますが、ここに空白があるのは意図的なものなので消してはいけません。

k-takata commented 4 years ago

https://github.com/vim-jp/issues/issues/1321#issuecomment-566072302

- :map <F4> o#include  
+ :map <F4> o#include

これもでした。

tsuyoshicho commented 4 years ago

たしかに本文からスペース込みでしたね...

h-east commented 4 years ago

from https://github.com/vim-jp/vimdoc-ja-working/pull/807/files 「12. GUI Toolbar Images」が見出しにないですね。(そして以降の番号も1つずつ増やす必要がある)

diff --git a/runtime/doc/os_haiku.txt b/runtime/doc/os_haiku.txt
index 2c02994d5..3e4938f66 100644
--- a/runtime/doc/os_haiku.txt
+++ b/runtime/doc/os_haiku.txt
@@ -25,8 +25,9 @@ targets personal computing.
  9. The meta key modifier  |haiku-meta|
 10. Mouse key mappings     |haiku-mouse|
 11. Color names            |haiku-colors|
-12. Credits            |haiku-support-credits|
-13. Bugs & to-do       |haiku-bugs|
+12. GUI Toolbar Images     |haiku-toolbar-images|
+13. Credits            |haiku-support-credits|
+14. Bugs & to-do       |haiku-bugs|

 1. General                     *haiku-general*
@@ -221,7 +222,7 @@ All the changes and patches released under vim-license.
 Thank you, all!

-13. Bugs & to-do                   *haiku-bugs*
+14. Bugs & to-do                   *haiku-bugs*

 The port is under development now and far away from the perfect state. For bug
 reports, patches and wishes, please use the Vim mailing list or Vim Github
k-takata commented 4 years ago

ここまでの分を報告しました。https://github.com/vim/vim/pull/6020

k-takata commented 4 years ago

取り込まれました。https://github.com/vim/vim/commit/7ceefb35c8110d87ced884275ddbe63d024a014f

h-east commented 4 years ago

提案。 8.2.0555で対応したVim9のリストと辞書の自動行継続(:helpg Automatic line continuation)のhelpからline-continuationを参照したほうが良いと思った。

diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt
index cb880c18f..70b4e5d4d 100644
--- a/runtime/doc/vim9.txt
+++ b/runtime/doc/vim9.txt
@@ -282,7 +282,7 @@ number of arguments and any return type.  The function can be defined later.
 Automatic line continuation ~

 In many cases it is obvious that an expression continues on the next line.  In
-those cases there is no need to prefix the line with a backslash.  For
+those cases there is no need to |line-continuation| with a backslash.  For
 example, when a list spans multiple lines: >
    let mylist = [
        'one',

(追記) 8.2.1388の前のRuntimeファイル更新で反映済。

h-east commented 4 years ago

typo in 8.2.0562

s/iin/in/

diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt
index cb880c18f..2e284e8b2 100644
--- a/runtime/doc/vim9.txt
+++ b/runtime/doc/vim9.txt
@@ -299,7 +299,7 @@ Function call: >
            arg2
            )

-For binary operators iin expressions not in [], {} or () a line break is
+For binary operators in expressions not in [], {} or () a line break is
 possible AFTER the operators.  For example: >
    let text = lead ..
           middle ..

(追記) 8.2.1042 で修正済

k-takata commented 4 years ago

no need to |line-continuation| with a backslash.

は文法的におかしいので、

no need to prefix the line with a backslash |line-continuation|.

としておくのが無難かなと思います。

tsuyoshicho commented 4 years ago

typo in 8.2.0910

diff --git runtime/doc/eval.txt runtime/doc/eval.txt
index 99b17a16b..1a908e978 100644
--- runtime/doc/eval.txt
+++ runtime/doc/eval.txt
@@ -8572,7 +8572,8 @@ searchcount([{options}])                                  *searchcount()*
                  pos           |List|          `[lnum, col, off]` value
                                                when recomputing the result.
                                                this changes "current" result
-                                               value. see |cursor()|, |getpos()
+                                               value. see |cursor()|,
+                                               |getpos()|
                                                (default: cursor's position)

@@ -9185,7 +9186,7 @@ settagstack({nr}, {dict} [, {action}])                    *settagstack()*

                Returns zero for success, -1 for failure.

-               Examples (for more examples see |tagstack-examples||):
+               Examples (for more examples see |tagstack-examples|):
                    Empty the tag stack of window 3: >
                        call settagstack(3, {'items' : []})

(追記) 8.2.1388の前のRuntimeファイル更新で反映済。

h-east commented 4 years ago

他の 'cinoptions'の値と同様にヘルプラベルを追加。

diff --git a/runtime/doc/indent.txt b/runtime/doc/indent.txt
index c4785c4b2..baa6ffdde 100644
--- a/runtime/doc/indent.txt
+++ b/runtime/doc/indent.txt
@@ -569,7 +569,7 @@ The examples below assume a 'shiftwidth' of 4.
          recognize preprocessor lines; right-shifting lines that start
          with "#" does not work.

-
+                               *cino-P*
    PN    When N is non-zero recognize C pragmas, and indent them like any
          other code; does not concern other preprocessor directives.
          When N is zero (default): don't recognize C pragmas, treating

(追記) 8.2.1388の前のRuntimeファイル更新で反映済。

tsuyoshicho commented 4 years ago

typo in 8.2.0910

diff --git runtime/doc/if_lua.txt runtime/doc/if_lua.txt
index 63e227d30..3a4007c29 100644
--- runtime/doc/if_lua.txt
+++ runtime/doc/if_lua.txt
@@ -199,8 +199,8 @@ Vim evaluation and command execution, and others.
                                returns it. Note that the buffer is not set as
                                current.

-       vim.call({name} [,{args}])
-                               Proxy to call Vim function named {name} with 
+       vim.call({name} [, {args}])
+                               Proxy to call Vim function named {name} with
                                arguments {args}.  Example: >
                                        :lua print(vim.call('has', 'timers'))
 <

(追記) 8.2.1388の前のRuntimeファイル更新で反映済。

tsuyoshicho commented 4 years ago

typo in 8.2.1045

ここで議題になった、文意がおかしい点が、おそらくtypoだろうと思われます。

diff --git runtime/doc/eval.txt runtime/doc/eval.txt
index 6057b57c..784d6e30 100644
--- runtime/doc/eval.txt
+++ runtime/doc/eval.txt
@@ -9078,7 +9078,7 @@ setqflist({list} [, {action} [, {what}]])   *setqflist()*
    argument is ignored.  See below for the supported items in
    {what}.

-   When {what} is not present, the items in {list} or used.  Each
+   When {what} is not present, the items in {list} are used.  Each
    item must be a dictionary.  Non-dictionary items in {list} are
    ignored.  Each dictionary item can contain the following
    entries:

(追記) 8.2.1388の前のRuntimeファイル更新で反映済。

tsuyoshicho commented 4 years ago

typo in 8.2.1045

ここで議題になった、項目の不一致が、おそらくtypoだろうと思われます。

diff --git runtime/doc/options.txt runtime/doc/options.txt
index 4e78a2fa..6991a5f4 100644
--- runtime/doc/options.txt
+++ runtime/doc/options.txt
@@ -8366,7 +8366,7 @@ A jump table for the options with a short description can be found at |Q_op|.
  >= 14 Anything pending in a ":finally" clause.
  >= 15 Every executed Ex command from a script (truncated at 200
    characters).
- >= 16 Every executed Ex command
+ >= 16 Every executed Ex command.

  This option can also be set with the "-V" argument.  See |-V|.
  This option is also set by the |:verbose| command.

(追記) 8.2.1388の前のRuntimeファイル更新で反映済。

tsuyoshicho commented 4 years ago

typo in 8.2.1045 目次の項目は問題なし

diff --git runtime/doc/eval.txt runtime/doc/eval.txt
index 6057b57c..adab19ab 100644
--- runtime/doc/eval.txt
+++ runtime/doc/eval.txt
@@ -5415,7 +5415,7 @@ getloclist({nr} [, {what}])       *getloclist()*
          |location-list-file-window| for more
          details.

-getmarklist([{expr}]         *getmarklist()*
+getmarklist([{expr}])          *getmarklist()*
    Without the {expr} argument returns a |List| with information
    about all the global marks. |mark|

(追記) 8.2.1388の前のRuntimeファイル更新で反映済。

tsuyoshicho commented 4 years ago

typo in 8.2.1149 他は変更してるのに、ここは漏れてる

diff --git runtime/doc/usr_toc.txt runtime/doc/usr_toc.txt
index b17a87de..816cf065 100644
--- runtime/doc/usr_toc.txt
+++ runtime/doc/usr_toc.txt
@@ -333,7 +333,7 @@ Make Vim work as you like it.
    |44.11| Installing a syntax file
    |44.12| Portable syntax file layout

-|usr_45.txt|  Select your language
+|usr_45.txt|  Select your language (locale)
    |45.1|  Language for Messages
    |45.2|  Language for Menus
    |45.3|  Using another encoding
diff --git runtime/doc/usr_41.txt runtime/doc/usr_41.txt
index bde1dd1d..f4102039 100644
--- runtime/doc/usr_41.txt
+++ runtime/doc/usr_41.txt
@@ -44,7 +44,7 @@ script file.  You can think of other uses yourself.
  If you are familiar with Python, you can find a comparison between
  Python and Vim script here, with pointers to other documents:
     https://gist.github.com/yegappan/16d964a37ead0979b05e655aa036cad0
- And if you are familiar with Javascript:
+ And if you are familiar with JavaScript:
     https://w0rp.com/blog/post/vim-script-for-the-javascripter/

 Let's start with a simple example: >

(追記) 8.2.1388の前のRuntimeファイル更新で反映済。

tsuyoshicho commented 4 years ago

ピリオドと空白 in 8.2.1149

diff --git runtime/doc/usr_46.txt runtime/doc/usr_46.txt
index b05a660b9..2a3e2185f 100644
--- runtime/doc/usr_46.txt
+++ runtime/doc/usr_46.txt
@@ -34,7 +34,7 @@ That makes very clear what is defined where.
 Let's start with an example, a script that exports one function and has one
 private function: >

- vim9script  " This indicates a Vim9 script file, 
+ vim9script  " This indicates a Vim9 script file.

  export def GetMessage(): string
     let result = ''

(追記) 8.2.1388の前のRuntimeファイル更新で反映済。

kuuote commented 4 years ago

番号のドット抜けです

diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt
index b14ff0b10..fef9682fa 100644
--- a/runtime/doc/vim9.txt
+++ b/runtime/doc/vim9.txt
@@ -14,7 +14,7 @@ features in Vim9 script.
 THIS IS STILL UNDER DEVELOPMENT - ANYTHING CAN BREAK - ANYTHING CAN CHANGE

-1   What is Vim9 script?       |vim9-script|
+1.  What is Vim9 script?       |vim9-script|
 2.  Differences                |vim9-differences|
 3.  New style functions            |fast-functions|
 4.  Types              |vim9-types|

(追記) 8.2.1388の前のRuntimeファイル更新で反映済。

tsuyoshicho commented 4 years ago

typo in 8.2.1288

diff --git runtime/doc/syntax.txt runtime/doc/syntax.txt
index 2096a34b5..b192a67a1 100644
--- runtime/doc/syntax.txt
+++ runtime/doc/syntax.txt
@@ -3648,7 +3648,7 @@ DEFINING FOLDLEVEL          *:syn-foldlevel*
  start:    Use level of item containing start of line.
  minimum:  Use lowest local-minimum level of items on line.

- The default is 'start'.  Use 'minimum' to search a line horizontally
+ The default is "start".  Use "minimum" to search a line horizontally
  for the lowest level contained on the line that is followed by a
  higher level.  This produces more natural folds when syntax items
  may close and open horizontally within a line.

see https://github.com/vim-jp/vimdoc-ja-working/pull/836#discussion_r460375995


(追記) 8.2.1388の前のRuntimeファイル更新で反映済。

h-east commented 4 years ago

@tsuyoshicho 貼り付けられているdiffのタブがスペースに変換されていてうまくpatchがあてられないです。例えば: https://github.com/vim-jp/issues/issues/1321#issuecomment-640154029 diff作成時かペースト時にミスっていると思われます。次回確認お願いします。

h-east commented 4 years ago

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


(追記) 報告分は、8.2.1388の前のRuntimeファイル更新で取り込まれました。

tsuyoshicho commented 4 years ago

@tsuyoshicho 貼り付けられているdiffのタブがスペースに変換されていてうまくpatchがあてられないです。

diff作成時かペースト時にミスっていると思われます。次回確認お願いします。

了解です。 すみません、お手数おかけしました。

tennashi commented 4 years ago

in 8.2.1378

diff --git a/runtime/doc/channel.txt b/runtime/doc/channel.txt
index 84a344fa9..ef009ec21 100644
--- a/runtime/doc/channel.txt
+++ b/runtime/doc/channel.txt
@@ -1282,13 +1282,13 @@ prompt. >
          " Send the text to a shell with Enter appended.
          call ch_sendraw(g:shell_job, a:text .. "\n")
        endfunc
-
+
        " Function handling output from the shell: Added above the prompt.
        func GotOutput(channel, msg)
          call append(line("$") - 1, "- " . a:msg)
        endfunc

-       " Function handling the shell exist: close the window.
+       " Function handling the shell exit: close the window.
        func JobExit(job, status)
          quit!
        endfunc

余分な空白 && exist じゃなくて exit かな、と

tsuyoshicho commented 4 years ago

他のif_*.txtの記述と合せる。

in Vim 8.2.1471

diff --git runtime/doc/if_mzsch.txt runtime/doc/if_mzsch.txt
index 6420856a..161f6b9a 100644
--- runtime/doc/if_mzsch.txt
+++ runtime/doc/if_mzsch.txt
@@ -43,7 +43,7 @@ To speed up the process, you might also want to use --disable-gracket and
 {script}
 {endmarker}
            Execute inlined MzScheme script {script}.
-           Note: This command doesn't work if the MzScheme
+           Note: This command doesn't work when the MzScheme
            feature wasn't compiled in.  To avoid errors, see
            |script-here|.
tsuyoshicho commented 4 years ago

他の箇所の空白の開け方、code blockの終了の仕方に合わせています。 in Vim 8.2.1471

diff --git runtime/doc/eval.txt runtime/doc/eval.txt
index 079eecb9..1b02ab7c 100644
--- runtime/doc/eval.txt
+++ runtime/doc/eval.txt
@@ -3073,7 +3073,7 @@ appendbufline({expr}, {lnum}, {text})         *appendbufline()*
        If {expr} is not a valid buffer or {lnum} is not valid, an
        error message is given. Example: >
            :let failed = appendbufline(13, 0, "# THE START")
-<
+
 <      Can also be used as a |method| after a List, the base is
        passed as the second argument: >
            mylist->appendbufline(buf, lnum)
tsuyoshicho commented 4 years ago

in Vim 8.2.1471

diff --git runtime/doc/eval.txt runtime/doc/eval.txt
index 079eecb9..9c2896fc 100644
--- runtime/doc/eval.txt
+++ runtime/doc/eval.txt
@@ -10497,8 +10497,8 @@ terminalprops()                     *terminalprops()*
        detected from the response to |t_RV| request.  See
        |v:termresponse| for the response itself.  If |v:termresponse|
        is empty most values here will be 'u' for unknown.
-          cursor_style     wether sending |t_RS| works  **
-          cursor_blink_mode    wether sending |t_RC| works  **
+          cursor_style     whether sending |t_RS| works  **
+          cursor_blink_mode    whether sending |t_RC| works  **
           underline_rgb    whether |t_8u| works **
           mouse        mouse type supported
tsuyoshicho commented 4 years ago

説明の他の箇所は全部 "%" なので、まあtypo確実かと in Vim 8.2.1471

diff --git runtime/doc/various.txt runtime/doc/various.txt
index b0e5e8516..e19c5964d 100644
--- runtime/doc/various.txt
+++ runtime/doc/various.txt
@@ -255,7 +255,7 @@ g8          Print the hex values of the bytes used in the
            Special characters in the file name are not escaped,
            use quotes to avoid their special meaning: >
                :!ls "%"
-<          If the file name contains a "$" then single quotes
+<          If the file name contains a "%" then single quotes
            might work better, but this only works if the file
            name does not contain a single quote: >
                :!ls '%'
k-takata commented 4 years ago

いや、これは $ でいいはず。 例えば、$PATH.txt というファイル名を編集していたとすると、:!ls "%":!ls "$PATH.txt" に展開されて実行されます。すると、シェルが $PATH を展開してしまって想定外のコマンドが実行されてしまいます。 それを避けるには :!ls '%' とすればよいという話です。

tsuyoshicho commented 4 years ago

ああ、なるほど、それはそうか、ややこしいw

tsuyoshicho commented 4 years ago

タブと空白の違い(他の行はタブで間の空白を制御している) in Vim 8.2.1511

diff --git runtime/doc/tabpage.txt runtime/doc/tabpage.txt
index 5a2ed2e81..5c0d0edfd 100644
--- runtime/doc/tabpage.txt
+++ runtime/doc/tabpage.txt
@@ -259,7 +259,7 @@ REORDERING TAB PAGES:
            :tabmove    " move the tab page to the last
            :$tabmove   " as above
            :tabmove $  " as above
-           :tabmove #  " move the tab page after the last accessed
+           :tabmove #  " move the tab page after the last accessed
                " tab page

 :tabm[ove] +[N]
tsuyoshicho commented 4 years ago

in Vim 8.2.1678

diff --git runtime/doc/eval.txt runtime/doc/eval.txt
index 68884ba1..e2819a22 100644
--- runtime/doc/eval.txt
+++ runtime/doc/eval.txt
@@ -120,7 +120,7 @@ base, use |str2nr()|.

                        *TRUE* *FALSE* *Boolean*
 For boolean operators Numbers are used.  Zero is FALSE, non-zero is TRUE.
-You can also use |v:false| and |v:true|.  In Vim9 script |false| and |true|. 
+You can also use |v:false| and |v:true|.  In Vim9 script |false| and |true|.
 When TRUE is returned from a function it is the Number one, FALSE is the
 number zero.

@@ -7863,7 +7863,7 @@ printf({fmt}, {expr1} ...)                *printf()*

 prompt_getprompt({buf})                    *prompt_getprompt()*
        Returns the effective prompt text for buffer {buf}. {buf} can
-       be a buffer name or number. |prompt-buffer|.
+       be a buffer name or number. |prompt-buffer|

        If the buffer doesn't exist or isn't a prompt buffer, an empty
        string is returned.
mityu commented 3 years ago

Vim 8.2.1770 です。 第一引数は必須かと。 https://github.com/vim/vim/blob/d569a9e74684cd17f9cea63e804281388728e513/src/evalfunc.c#L826

diff --git a/runtime/doc/textprop.txt b/runtime/doc/textprop.txt
index ac6d12a69..7dadbca76 100644
--- a/runtime/doc/textprop.txt
+++ b/runtime/doc/textprop.txt
@@ -101,7 +101,7 @@ Manipulating text property types:
 prop_type_add({name}, {props})         define a new property type
 prop_type_change({name}, {props})      change an existing property type
 prop_type_delete({name} [, {props}])   delete a property type
-prop_type_get([{name} [, {props}]])    get property type values
+prop_type_get({name} [, {props}])      get property type values
 prop_type_list([{props}])              get list of property types

@@ -291,7 +291,7 @@ prop_type_delete({name} [, {props}])                        *prop_type_
delete()*
                Can also be used as a |method|: >
                        GetPropName()->prop_type_delete()

-prop_type_get([{name} [, {props}]])                    *prop_type_get()*
+prop_type_get({name} [, {props}])                      *prop_type_get()*
                Returns the properties of property type {name}.  This is a
                dictionary with the same fields as was given to
                prop_type_add().
h-east commented 3 years ago

from https://github.com/vim-jp/vimdoc-ja-working/pull/852 1st: :tabnext $の後ろに追加しないと:tabnext $の説明があわなくなる。 2nd: 余計な空白を削除。

diff --git a/runtime/doc/tabpage.txt b/runtime/doc/tabpage.txt
index 5a2ed2e81..e1b92c721 100644
--- a/runtime/doc/tabpage.txt
+++ b/runtime/doc/tabpage.txt
@@ -195,8 +195,8 @@ gt                  *i_CTRL-<PageDown>* *i_<C-PageDown>*
            :+2tabnext  " go to the two next tab page
            :1tabnext   " go to the first tab page
            :$tabnext   " go to the last tab page
-           :tabnext #  " go to the last accessed tab page
            :tabnext $  " as above
+           :tabnext #  " go to the last accessed tab page
            :tabnext -  " go to the previous tab page
            :tabnext -1 " as above
            :tabnext +  " go to the next tab page
@@ -225,7 +225,7 @@ gT      Go to the previous tab page.  Wraps around from the first one
                            *:tabl* *:tablast*
 :tabl[ast] Go to the last tab page.

-                       *g<Tab>* *CTRL-W_g<Tab>* *<C-Tab>*
+                   *g<Tab>* *CTRL-W_g<Tab>* *<C-Tab>*
 g<Tab>     Go to the last accessed tab page.

 Other commands:
h-east commented 3 years ago

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

h-east commented 3 years ago

s/Names/NAMES/

diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt
index fdbcefcd9..973fbb893 100644
--- a/runtime/doc/vim9.txt
+++ b/runtime/doc/vim9.txt
@@ -282,7 +282,7 @@ The constant only applies to the value itself, not what it refers to. >
    NAMES[0] = ["Jack"]     # Error!
    NAMES[0][0] = "Jack"    # Error!
    NAMES[1] = ["Emma"]     # Error!
-   Names[1][0] = "Emma"    # OK, now females[0] == "Emma"
+   NAMES[1][0] = "Emma"    # OK, now females[0] == "Emma"

 <                          *E1092*
 Declaring more than one variable at a time, using the unpack notation, is
h-east commented 3 years ago

from https://github.com/vim-jp/vimdoc-ja-working/pull/862 改行位置修正。

diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index 6f594ab81..a3266c5b6 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -3511,8 +3511,8 @@ byteidxcomp({expr}, {nr})                 *byteidxcomp()*
 <      The first and third echo result in 3 ('e' plus composing
        character is 3 bytes), the second echo results in 1 ('e' is
        one byte).
-       Only works differently from byteidx() when 'encoding' is set to
-       a Unicode encoding.
+       Only works differently from byteidx() when 'encoding' is set
+       to a Unicode encoding.

        Can also be used as a |method|: >
            GetName()->byteidxcomp(idx)
h-east commented 3 years ago

from https://github.com/vim-jp/vimdoc-ja-working/pull/864 空白をタブ文字に変更。 (2021-01-07 h-east): patch更新。from https://github.com/vim-jp/vimdoc-ja-working/pull/864#pullrequestreview-558268778

diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt
index b30db0b86..be52c7577 100644
--- a/runtime/doc/vim9.txt
+++ b/runtime/doc/vim9.txt
@@ -70,28 +70,28 @@ Overview ~
 Brief summary of the differences you will most often encounter when using Vim9
 script and `:def` functions; details are below:
 - Comments start with #, not ": >
-   echo "hello"   # comment
+   echo "hello"   # comment
 - Using a backslash for line continuation is hardly ever needed: >
-   echo "hello "
+   echo "hello "
         .. yourName
         .. ", how are you?"
 - White space is required in many places.
 - Assign values without `:let`, declare variables with `:var`: >
-   var count = 0
+   var count = 0
    count += 3
 - Constants can be declared with `:final` and `:const`: >
-   final matches = []        # add matches
+   final matches = []        # add matches
    const names = ['Betty', 'Peter']  # cannot be changed
 - `:final` cannot be used as an abbreviation of `:finally`.
 - Variables and functions are script-local by default.
 - Functions are declared with argument types and return type: >
    def CallMe(count: number, message: string): bool
 - Call functions without `:call`: >
-   writefile(['done'], 'file.txt')
+   writefile(['done'], 'file.txt')
 - You cannot use `:xit`, `:t`, `:append`, `:change`, `:insert` or curly-braces
   names.
 - A range before a command must be prefixed with a colon: >
-   :%s/this/that
+   :%s/this/that

 Comments starting with # ~
@@ -432,7 +432,7 @@ possible just before or after the operator.  For example: >
           .. middle
           .. end
    var total = start +
-               end -
+           end -
            correction
    var result = positive
            ? PosFunc(arg)
@@ -629,9 +629,9 @@ one: >

 When using "!" for inverting, there is no error for using any type and the
 result is a boolean.  "!!" can be used to turn any value into boolean: >
-   !'yes'              == false
+   !'yes'          == false
    !![]            == false
-   !![1, 2, 3]         == true
+   !![1, 2, 3]     == true

 When using "`.."` for string concatenation arguments of simple types are
 always converted to string: >
@@ -1055,14 +1055,14 @@ actually needed.  A recommended mechanism:

 1. In the plugin define user commands, functions and/or mappings that refer to
    an autoload script. >
-       command -nargs=1 SearchForStuff call searchfor#Stuff(<f-args>)
+   command -nargs=1 SearchForStuff call searchfor#Stuff(<f-args>)

 <   This goes in .../plugin/anyname.vim.  "anyname.vim" can be freely chosen.

 2. In the autoload script do the actual work.  You can import items from
    other files to split up functionality in appropriate pieces. >
    vim9script
-        import FilterFunc from "../import/someother.vim"
+   import FilterFunc from "../import/someother.vim"
    def searchfor#Stuff(arg: string)
      var filtered = FilterFunc(arg)
      ...
h-east commented 3 years ago

from https://github.com/vim-jp/vimdoc-ja-working/pull/868#pullrequestreview-563190326

間違い修正。weだとその位置にカーソル移動しない...

diff --git a/runtime/doc/usr_03.txt b/runtime/doc/usr_03.txt
index c3bf2d312..d30bddfc6 100644
--- a/runtime/doc/usr_03.txt
+++ b/runtime/doc/usr_03.txt
@@ -50,7 +50,7 @@ which moves to the previous end of a word:

    This is a line with example text ~
       <----<----x---->------------>
-      2ge   ge     e       we
+      2ge   ge     e       2e

 If you are at the last word of a line, the "w" command will take you to the
 first word in the next line.  Thus you can use this to move through a
h-east commented 3 years ago

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

tsuyoshicho commented 3 years ago

via Vim 8.2.2316

改訂 \text{(1,10]\text{(1,10]} かもしれない、とのこと なので合せたものに変更

diff --git runtime/doc/syntax.txt runtime/doc/syntax.txt
index c171a20ac..90feedd2a 100644
--- runtime/doc/syntax.txt
+++ runtime/doc/syntax.txt
@@ -3428,8 +3428,8 @@ syntax highlighting script handles this with the following logic:
  Tex: Match Check Control~

    Sometimes one actually wants mismatched parentheses, square braces,
-   and or curly braces; for example, \text{(1,10] is a range from but
-   not including 1 to and including 10}.  This wish, of course, conflicts
+   and or curly braces; for example, \text{(1,10]} is a range from but
+   not including 1 to and including 10.  This wish, of course, conflicts
    with the desire to provide delimiter mismatch detection.  To
    accommodate these conflicting goals, syntax/tex.vim provides >
        g:tex_matchcheck = '[({[]'

see https://github.com/vim-jp/vimdoc-ja-working/pull/871#discussion_r554323936


Fixed.