summaryrefslogtreecommitdiffstats
path: root/runtime/doc
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2020-08-07 19:54:59 +0200
committerBram Moolenaar <Bram@vim.org>2020-08-07 19:54:59 +0200
commite7b1ea0276cc83cd5c612f3189a174a60d57b5ed (patch)
treea8c3ded5f0cb0966c0385a716f4e82a9a81cb3be /runtime/doc
parent95dd9f2571f09a915674133c73b471b0ebbdcdbf (diff)
Update runtime files.
Diffstat (limited to 'runtime/doc')
-rw-r--r--runtime/doc/autocmd.txt6
-rw-r--r--runtime/doc/develop.txt6
-rw-r--r--runtime/doc/eval.txt34
-rw-r--r--runtime/doc/gui_w32.txt2
-rw-r--r--runtime/doc/helphelp.txt20
-rw-r--r--runtime/doc/if_lua.txt4
-rw-r--r--runtime/doc/if_tcl.txt4
-rw-r--r--runtime/doc/indent.txt28
-rw-r--r--runtime/doc/map.txt2
-rw-r--r--runtime/doc/options.txt18
-rw-r--r--runtime/doc/os_vms.txt2
-rw-r--r--runtime/doc/popup.txt8
-rw-r--r--runtime/doc/remote.txt2
-rw-r--r--runtime/doc/syntax.txt16
-rw-r--r--runtime/doc/tags1
-rw-r--r--runtime/doc/todo.txt27
-rw-r--r--runtime/doc/usr_04.txt2
-rw-r--r--runtime/doc/usr_05.txt4
-rw-r--r--runtime/doc/usr_20.txt8
-rw-r--r--runtime/doc/usr_30.txt2
-rw-r--r--runtime/doc/usr_31.txt6
-rw-r--r--runtime/doc/usr_40.txt8
-rw-r--r--runtime/doc/usr_41.txt4
-rw-r--r--runtime/doc/usr_42.txt4
-rw-r--r--runtime/doc/usr_46.txt2
-rw-r--r--runtime/doc/usr_toc.txt2
-rw-r--r--runtime/doc/vim9.txt39
-rw-r--r--runtime/doc/visual.txt8
28 files changed, 146 insertions, 123 deletions
diff --git a/runtime/doc/autocmd.txt b/runtime/doc/autocmd.txt
index b0d791927f..d56f211d0d 100644
--- a/runtime/doc/autocmd.txt
+++ b/runtime/doc/autocmd.txt
@@ -1,4 +1,4 @@
-*autocmd.txt* For Vim version 8.2. Last change: 2020 Jun 10
+*autocmd.txt* For Vim version 8.2. Last change: 2020 Aug 02
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -1425,8 +1425,8 @@ name!
:aug[roup]! {name} Delete the autocmd group {name}. Don't use
this if there is still an autocommand using
this group! You will get a warning if doing
- it anyway. when the group is the current group
- you will get error E936.
+ it anyway. When the group is the current
+ group you will get error E936.
To enter autocommands for a specific group, use this method:
1. Select the group with ":augroup {name}".
diff --git a/runtime/doc/develop.txt b/runtime/doc/develop.txt
index 7ed251a6f6..f139ebe5e6 100644
--- a/runtime/doc/develop.txt
+++ b/runtime/doc/develop.txt
@@ -1,4 +1,4 @@
-*develop.txt* For Vim version 8.2. Last change: 2020 Apr 13
+*develop.txt* For Vim version 8.2. Last change: 2020 Jul 27
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -34,8 +34,8 @@ balance must be found between them.
VIM IS... VI COMPATIBLE *design-compatible*
First of all, it should be possible to use Vim as a drop-in replacement for
-Vi. When the user wants to, he can use Vim in compatible mode and hardly
-notice any difference with the original Vi.
+Vi. When the user wants to, Vim can be used in compatible mode and hardly
+any differences with the original Vi will be noticed.
Exceptions:
- We don't reproduce obvious Vi bugs in Vim.
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index 8c6f7ded6b..5bb763a4a4 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -1,4 +1,4 @@
-*eval.txt* For Vim version 8.2. Last change: 2020 Aug 01
+*eval.txt* For Vim version 8.2. Last change: 2020 Aug 07
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -4895,31 +4895,32 @@ getbufinfo([{dict}])
Each returned List item is a dictionary with the following
entries:
- bufnr buffer number.
+ bufnr Buffer number.
changed TRUE if the buffer is modified.
- changedtick number of changes made to the buffer.
+ changedtick Number of changes made to the buffer.
hidden TRUE if the buffer is hidden.
- lastused timestamp in seconds, like
+ lastused Timestamp in seconds, like
|localtime()|, when the buffer was
last used.
{only with the |+viminfo| feature}
listed TRUE if the buffer is listed.
- lnum current line number in buffer.
- linecount number of lines in the buffer (only
+ lnum Line number used for the buffer when
+ opened in the current window.
+ linecount Number of lines in the buffer (only
valid when loaded)
loaded TRUE if the buffer is loaded.
- name full path to the file in the buffer.
- signs list of signs placed in the buffer.
+ name Full path to the file in the buffer.
+ signs List of signs placed in the buffer.
Each list item is a dictionary with
the following fields:
id sign identifier
lnum line number
name sign name
- variables a reference to the dictionary with
+ variables A reference to the dictionary with
buffer-local variables.
- windows list of |window-ID|s that display this
+ windows List of |window-ID|s that display this
buffer
- popups list of popup |window-ID|s that
+ popups List of popup |window-ID|s that
display this buffer
Examples: >
@@ -5446,7 +5447,7 @@ getloclist({nr} [, {what}]) *getloclist()*
:echo getloclist(5, {'filewinid': 0})
-getmarklist([{expr}] *getmarklist()*
+getmarklist([{expr}]) *getmarklist()*
Without the {expr} argument returns a |List| with information
about all the global marks. |mark|
@@ -8709,7 +8710,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)
@@ -9111,7 +9113,7 @@ setqflist({list} [, {action} [, {what}]]) *setqflist()*
argument is ignored. See below for the supported items in
{what}.
*setqflist-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:
@@ -9332,7 +9334,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' : []})
@@ -10132,7 +10134,7 @@ swapname({expr}) *swapname()*
The result is the swap file path of the buffer {expr}.
For the use of {expr}, see |bufname()| above.
If buffer {expr} is the current buffer, the result is equal to
- |:swapname| (unless no swap file).
+ |:swapname| (unless there is no swap file).
If buffer {expr} has no swap file, returns an empty string.
Can also be used as a |method|: >
diff --git a/runtime/doc/gui_w32.txt b/runtime/doc/gui_w32.txt
index 30e2287826..c0f8867739 100644
--- a/runtime/doc/gui_w32.txt
+++ b/runtime/doc/gui_w32.txt
@@ -451,7 +451,7 @@ with the Intellimouse driver 2.2 and when "Universal Scrolling" is turned on.
XPM support *w32-xpm-support*
-GVim can be build on MS-Windows with support for XPM files. |+xpm_w32|
+GVim can be built on MS-Windows with support for XPM files. |+xpm_w32|
See the Make_mvc.mak file for instructions, search for XPM.
To try out if XPM support works do this: >
diff --git a/runtime/doc/helphelp.txt b/runtime/doc/helphelp.txt
index 7771a505ba..8dcaa1f509 100644
--- a/runtime/doc/helphelp.txt
+++ b/runtime/doc/helphelp.txt
@@ -1,4 +1,4 @@
-*helphelp.txt* For Vim version 8.2. Last change: 2020 Mar 01
+*helphelp.txt* For Vim version 8.2. Last change: 2020 Jul 27
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -369,14 +369,16 @@ highlighting. So do these:
You can find the details in $VIMRUNTIME/syntax/help.vim
*inclusion*
-Some people make a big deal about using "his" when referring to the user,
-thinking it means we assume the user is male. That is of course not the case,
-it's just a habit of writing help text, which quite often is many years old.
-Also, a lot of the text is written by contributors for who English is not
-their first language. We do not make any assumptions about the gender of the
-user, no matter how the text is phrased. And we do not want to waste time on
-this discussion. The goal is that the reader understands how Vim works, the
-exact wording is secondary.
+Vim is for everybody, no matter race, gender or anything. Some people make a
+big deal about using "he" or "his" when referring to the user, thinking it
+means we assume the user is male. That is not the case, it's just a habit of
+writing help text, which quite often is many years old. Also, a lot of the
+text is written by contributors for whom English is not their first language.
+We do not make any assumptions about the gender of the user, no matter how the
+text is phrased. Some people have suggested using "they", but that is not
+regular English. We do not want to spend much time on this discussion. The
+goal is that the reader understands how Vim works, the exact wording is
+secondary.
vim:tw=78:ts=8:noet:ft=help:norl:
diff --git a/runtime/doc/if_lua.txt b/runtime/doc/if_lua.txt
index 65a2d60430..b556996985 100644
--- a/runtime/doc/if_lua.txt
+++ b/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'))
<
diff --git a/runtime/doc/if_tcl.txt b/runtime/doc/if_tcl.txt
index 60ac6bcc5e..90dec9dba1 100644
--- a/runtime/doc/if_tcl.txt
+++ b/runtime/doc/if_tcl.txt
@@ -275,7 +275,7 @@ Options:
$win delcmd {cmd} *tcl-window-delcmd*
Registers the Tcl command {cmd} as a deletion callback for the window.
This command is executed (in the global scope) just before the window
- is closed. Complex commands should be build with "list": >
+ is closed. Complex commands should be built with "list": >
$win delcmd [list puts vimerr "window deleted"]
< See also |tcl-buffer-delcmd|.
@@ -357,7 +357,7 @@ Options:
$buf delcmd {cmd} *tcl-buffer-delcmd*
Registers the Tcl command {cmd} as a deletion callback for the buffer.
This command is executed (in the global scope) just before the buffer
- is deleted. Complex commands should be build with "list": >
+ is deleted. Complex commands should be built with "list": >
$buf delcmd [list puts vimerr "buffer [$buf number] gone"]
< See also |tcl-window-delcmd|.
diff --git a/runtime/doc/indent.txt b/runtime/doc/indent.txt
index c4785c4b22..87d5c0bd5e 100644
--- a/runtime/doc/indent.txt
+++ b/runtime/doc/indent.txt
@@ -414,11 +414,11 @@ The examples below assume a 'shiftwidth' of 4.
<
*cino-(*
(N When in unclosed parentheses, indent N characters from the line
- with the unclosed parentheses. Add a 'shiftwidth' for every
+ with the unclosed parenthesis. Add a 'shiftwidth' for every
extra unclosed parentheses. When N is 0 or the unclosed
- parentheses is the first non-white character in its line, line
+ parenthesis is the first non-white character in its line, line
up with the next non-white character after the unclosed
- parentheses. (default 'shiftwidth' * 2).
+ parenthesis. (default 'shiftwidth' * 2).
cino= cino=(0 >
if (c1 && (c2 || if (c1 && (c2 ||
@@ -439,7 +439,7 @@ The examples below assume a 'shiftwidth' of 4.
<
*cino-U*
UN When N is non-zero, do not ignore the indenting specified by
- ( or u in case that the unclosed parentheses is the first
+ ( or u in case that the unclosed parenthesis is the first
non-white character in its line. (default 0).
cino= or cino=(s cino=(s,U1 >
@@ -452,8 +452,8 @@ The examples below assume a 'shiftwidth' of 4.
*cino-w*
wN When in unclosed parentheses and N is non-zero and either
using "(0" or "u0", respectively, or using "U0" and the unclosed
- parentheses is the first non-white character in its line, line
- up with the character immediately after the unclosed parentheses
+ parenthesis is the first non-white character in its line, line
+ up with the character immediately after the unclosed parenthesis
rather than the first non-white character. (default 0).
cino=(0 cino=(0,w1 >
@@ -464,11 +464,11 @@ The examples below assume a 'shiftwidth' of 4.
<
*cino-W*
WN When in unclosed parentheses and N is non-zero and either
- using "(0" or "u0", respectively and the unclosed parentheses is
+ using "(0" or "u0", respectively and the unclosed parenthesis is
the last non-white character in its line and it is not the
- closing parentheses, indent the following line N characters
+ closing parenthesis, indent the following line N characters
relative to the outer context (i.e. start of the line or the
- next unclosed parentheses). (default: 0).
+ next unclosed parenthesis). (default: 0).
cino=(0 cino=(0,W4 >
a_long_line( a_long_line(
@@ -495,8 +495,8 @@ The examples below assume a 'shiftwidth' of 4.
<
*cino-m*
mN When N is non-zero, line up a line starting with a closing
- parentheses with the first character of the line with the
- matching opening parentheses. (default 0).
+ parenthesis with the first character of the line with the
+ matching opening parenthesis. (default 0).
cino=(s cino=(s,m1 >
c = c1 && ( c = c1 && (
@@ -510,7 +510,7 @@ The examples below assume a 'shiftwidth' of 4.
<
*cino-M*
MN When N is non-zero, line up a line starting with a closing
- parentheses with the first character of the previous line.
+ parenthesis with the first character of the previous line.
(default 0).
cino= cino=M1 >
@@ -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
@@ -996,7 +996,7 @@ Indent after a nested paren: >
Indent for a continuation line: >
let g:pyindent_continue = 'shiftwidth() * 2'
-The method uses |searchpair()| to look back for unclosed parenthesis. This
+The method uses |searchpair()| to look back for unclosed parentheses. This
can sometimes be slow, thus it timeouts after 150 msec. If you notice the
indenting isn't correct, you can set a larger timeout in msec: >
let g:pyindent_searchpair_timeout = 500
diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt
index 79c46f7125..78451a1406 100644
--- a/runtime/doc/map.txt
+++ b/runtime/doc/map.txt
@@ -1,4 +1,4 @@
-*map.txt* For Vim version 8.2. Last change: 2020 Apr 23
+*map.txt* For Vim version 8.2. Last change: 2020 Aug 01
VIM REFERENCE MANUAL by Bram Moolenaar
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index d98307e30a..102eb62abd 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -1,4 +1,4 @@
-*options.txt* For Vim version 8.2. Last change: 2020 Jul 18
+*options.txt* For Vim version 8.2. Last change: 2020 Aug 07
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -2715,6 +2715,11 @@ A jump table for the options with a short description can be found at |Q_op|.
for Unix: ".,~/tmp,/var/tmp,/tmp")
global
List of directory names for the swap file, separated with commas.
+ Recommended value: ".,~/vimswap//" - this will put the swap file next
+ to the edited file if possible, and in your personal swap directory
+ otherwise. Make sure "~/vimswap//" is only readable for you.
+
+ Possible items:
- The swap file will be created in the first directory where this is
possible.
- Empty means that no swap file will be used (recovery is
@@ -2749,9 +2754,10 @@ A jump table for the options with a short description can be found at |Q_op|.
the same file twice will result in a warning. Using "/tmp" on Unix is
discouraged: When the system crashes you lose the swap file.
"/var/tmp" is often not cleared when rebooting, thus is a better
- choice than "/tmp". But it can contain a lot of files, your swap
- files get lost in the crowd. That is why a "tmp" directory in your
- home directory is tried first.
+ choice than "/tmp". But others on the computer may be able to see the
+ files, and it can contain a lot of files, your swap files get lost in
+ the crowd. That is why a "tmp" directory in your home directory is
+ tried first.
The use of |:set+=| and |:set-=| is preferred when adding or removing
directories from the list. This avoids problems when a future version
uses another default.
@@ -8368,7 +8374,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.
@@ -8907,7 +8913,7 @@ A jump table for the options with a short description can be found at |Q_op|.
{only available when compiled with the |terminal|
feature on MS-Windows}
Specifies the name of the winpty shared library, used for the
- |:terminal| command. The default depends on whether was build as a
+ |:terminal| command. The default depends on whether Vim was built as a
32-bit or 64-bit executable. If not found, "winpty.dll" is tried as
a fallback.
Environment variables are expanded |:set_env|.
diff --git a/runtime/doc/os_vms.txt b/runtime/doc/os_vms.txt
index 1682327839..b69f650b40 100644
--- a/runtime/doc/os_vms.txt
+++ b/runtime/doc/os_vms.txt
@@ -88,7 +88,7 @@ VAX C compiler is not fully ANSI C compatible in pre-processor directives
semantics, therefore you have to use a converter program that will do the lion
part of the job. For detailed instructions read file INSTALLvms.txt
-MMS_VIM.EXE is build together with VIM.EXE, but for XXD.EXE you should
+MMS_VIM.EXE is built together with VIM.EXE, but for XXD.EXE you should
change to a subdirectory and build it separately.
CTAGS is not part of the Vim source distribution anymore, however the OpenVMS
diff --git a/runtime/doc/popup.txt b/runtime/doc/popup.txt
index ff99fce9ab..8a0f2ba518 100644
--- a/runtime/doc/popup.txt
+++ b/runtime/doc/popup.txt
@@ -1,4 +1,4 @@
-*popup.txt* For Vim version 8.2. Last change: 2020 May 18
+*popup.txt* For Vim version 8.2. Last change: 2020 Jul 27
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -74,9 +74,9 @@ wrapping, lines in the buffer. It can be limited with the "maxheight"
property. You can use empty lines to increase the height or the "minheight"
property.
-The width of the window is normally equal to the longest line in the buffer.
-It can be limited with the "maxwidth" property. You can use spaces to
-increase the width or use the "minwidth" property.
+The width of the window is normally equal to the longest visible line in the
+buffer. It can be limited with the "maxwidth" property. You can use spaces
+to increase the width or use the "minwidth" property.
By default the 'wrap' option is set, so that no text disappears. Otherwise,
if there is not enough space then the window is shifted left in order to
diff --git a/runtime/doc/remote.txt b/runtime/doc/remote.txt
index 53c98d0e15..c6dcb98003 100644
--- a/runtime/doc/remote.txt
+++ b/runtime/doc/remote.txt
@@ -179,7 +179,7 @@ name on the 'VimRegistry' property on the root window.
A non GUI Vim with access to the X11 display (|xterm-clipboard| enabled), can
also act as a command server if a server name is explicitly given with the
---servername argument, or when Vim was build with the |+autoservername|
+--servername argument, or when Vim was built with the |+autoservername|
feature.
An empty --servername argument will cause the command server to be disabled.
diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt
index 8effaf55a0..a7f648cdf0 100644
--- a/runtime/doc/syntax.txt
+++ b/runtime/doc/syntax.txt
@@ -1,4 +1,4 @@
-*syntax.txt* For Vim version 8.2. Last change: 2020 Jul 08
+*syntax.txt* For Vim version 8.2. Last change: 2020 Jul 28
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -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.
@@ -3795,9 +3795,9 @@ DEFINING REGIONS *:syn-region* *:syn-start* *:syn-skip* *:syn-end*
[keepend]
[extend]
[excludenl]
- start={start_pattern} ..
- [skip={skip_pattern}]
- end={end_pattern} ..
+ start={start-pattern} ..
+ [skip={skip-pattern}]
+ end={end-pattern} ..
[{options}]
This defines one region. It may span several lines.
@@ -3819,12 +3819,12 @@ DEFINING REGIONS *:syn-region* *:syn-start* *:syn-skip* *:syn-end*
extend a containing match or item. Only
useful for end patterns. Must be given before
the patterns it applies to. |:syn-excludenl|
- start={start_pattern} The search pattern that defines the start of
+ start={start-pattern} The search pattern that defines the start of
the region. See |:syn-pattern| below.
- skip={skip_pattern} The search pattern that defines text inside
+ skip={skip-pattern} The search pattern that defines text inside
the region where not to look for the end
pattern. See |:syn-pattern| below.
- end={end_pattern} The search pattern that defines the end of
+ end={end-pattern} The search pattern that defines the end of
the region. See |:syn-pattern| below.
Example: >
diff --git a/runtime/doc/tags b/runtime/doc/tags
index 243b25ac60..02bb541f94 100644
--- a/runtime/doc/tags
+++ b/runtime/doc/tags
@@ -5744,6 +5744,7 @@ cino-J indent.txt /*cino-J*
cino-L indent.txt /*cino-L*
cino-M indent.txt /*cino-M*
cino-N indent.txt /*cino-N*
+cino-P indent.txt /*cino-P*
cino-U indent.txt /*cino-U*
cino-W indent.txt /*cino-W*
cino-^ indent.txt /*cino-^*
diff --git a/runtime/doc/todo.txt b/runtime/doc/todo.txt
index f9ebf2d58e..0c8d124592 100644
--- a/runtime/doc/todo.txt
+++ b/runtime/doc/todo.txt
@@ -1,4 +1,4 @@
-*todo.txt* For Vim version 8.2. Last change: 2020 Jul 26
+*todo.txt* For Vim version 8.2. Last change: 2020 Aug 05
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -39,10 +39,9 @@ browser use: https://github.com/vim/vim/issues/1234
-------------------- Known bugs and current work -----------------------
Making everything work:
-- more items in https://github.com/vim/vim/issues/6507
-- More "goto failed" with check for trylevel.
-- memory leak in test_vim9_script
- Check that when sourcing a Vim9 script, only the global items can be used.
+- Make string indexes character indexes instead of byte indexes. (#6574)
+ explain how to use byte index when needed. Use blob?
- :put with a "=" register argument doesn't work, need to find the expression
and compile it. (#6397)
- At the script level, keep script variables local to the block they are
@@ -51,6 +50,8 @@ Making everything work:
- Implement { } block at the script level.
- need to check type when a declaration specifies a type: #6507
let nr: number = 'asdf'
+- Make sure that in vim9script a function call without namespace only finds
+ the script-local function, not a global one.
- Make map() give an error if the resulting type is wrong.
Add mapnew() to create a new List/Dict for the result, which can have a
different value type.
@@ -169,7 +170,7 @@ Popup windows:
- Figure out the size and position better if wrapping inserts indent
Text properties:
-- :goto does not go to the right place when test properties are present.
+- :goto does not go to the right place when text properties are present.
(#5930)
- "cc" does not call inserted_bytes(). (Axel Forsman, #5763)
- Get E685 with a sequence of commands. (#5674)
@@ -200,7 +201,7 @@ Terminal debugger:
an already running program. (M. Kelly)
- When only gdb window exists, on "quit" edit another buffer.
- Use a sign group
-- Termdebug does not work when Vim was build with mzscheme: gdb hangs just
+- Termdebug does not work when Vim was built with mzscheme: gdb hangs just
after "run". Everything else works, including communication channel. Not
initializing mzscheme avoid the problem, thus it's not some #ifdef.
- Add support for lldb? issue #3565
@@ -255,10 +256,15 @@ Terminal emulator window:
Error numbers available:
E610, E611, E653
+Clean up empty entries in testdir/Make_all.mak
+
Remove SPACE_IN_FILENAME ? It is only used for completion.
Patch to use collaction based sorting. (Christian Brabandt, #6229)
+Add 'termguiattr' option, use "gui=" attributes in the terminal? Would work
+with 'termguicolors'. #1740
+
Can we detect true color support? https://gist.github.com/XVilka/8346728
Try setting a color then request the current color, like using t_u7.
@@ -333,6 +339,9 @@ character. (#6154)
undo result wrong: Masato Nishihata, #4798
+After recovering from a swap file the undofile should not be used, it causes
+corruption. (#6631)
+
When 'lazyredraw' is set sometimes the title is not updated.
(Jason Franklin, 2020 Feb 3) Looks like a race condition.
@@ -1471,7 +1480,7 @@ Zero-out krypt key information when no longer in use. (Ben Fritz, 2017 May 15)
Add stronger encryption. Could use libsodium (NaCl).
https://github.com/jedisct1/libsodium/
-Possibly include the needed code so that it can be build everywhere.
+Possibly include the needed code so that it can be built everywhere.
Add a way to restart a timer. It's similar to timer_stop() and timer_start(),
but the reference remains valid.
@@ -3833,8 +3842,6 @@ Macintosh:
8 When write_viminfo() is used while there are many orphaned viminfo
tempfiles writing the viminfo file fails. Give a clear error message so
that the user knows he has to delete the files.
-7 It's possible to redefine a script-local function with ":func
- <SNR>123_Test()". (Krishna) Disallow this.
I can't reproduce these (if you can, let me know how!):
@@ -5673,7 +5680,7 @@ Buffer list:
Also for other windows: ":inwin {winnr} {cmd}". How to make sure that
this works properly for all commands, and still be able to return to the
current buffer/window? E.g.: ":inbuf xxx only".
-8 Add File.{recent_files} menu entries: Recently edited files.
+8 Add File.{recent-files} menu entries: Recently edited files.
Ron Aaron has a plugin for this: mru.vim.
8 Unix: Check all uses of fnamecmp() and fnamencmp() if they should check
inode too.
diff --git a/runtime/doc/usr_04.txt b/runtime/doc/usr_04.txt
index 6a6cbcafad..d2dc056096 100644
--- a/runtime/doc/usr_04.txt
+++ b/runtime/doc/usr_04.txt
@@ -161,7 +161,7 @@ line break.
==============================================================================
*04.3* Repeating a change
-The "." command is one of the most simple yet powerful commands in Vim. It
+The "." command is one of the simplest yet powerful commands in Vim. It
repeats the last change. For instance, suppose you are editing an HTML file
and want to delete all the <B> tags. You position the cursor on the first <
and delete the <B> with the command "df>". You then go to the < of the next
diff --git a/runtime/doc/usr_05.txt b/runtime/doc/usr_05.txt
index 2cfff2449e..3a7438df4c 100644
--- a/runtime/doc/usr_05.txt
+++ b/runtime/doc/usr_05.txt
@@ -58,8 +58,8 @@ This initializes Vim for new users (as opposed to traditional Vi users). See
|defaults.vim| for the details.
The vimrc file can contain all the commands that you type after a colon. The
-most simple ones are for setting options. For example, if you want Vim to
-always start with the 'incsearch' option on, add this line your vimrc file: >
+simplest ones are for setting options. For example, if you want Vim to always
+start with the 'incsearch' option on, add this line your vimrc file: >
set incsearch
diff --git a/runtime/doc/usr_20.txt b/runtime/doc/usr_20.txt
index f99ffb51c8..ebad3c517f 100644
--- a/runtime/doc/usr_20.txt
+++ b/runtime/doc/usr_20.txt
@@ -327,10 +327,10 @@ for next.
==============================================================================
*20.5* Command line window
-Typing the text in the command line works different from typing text in Insert
-mode. It doesn't allow many commands to change the text. For most commands
-that's OK, but sometimes you have to type a complicated command. That's where
-the command line window is useful.
+Typing the text in the command line works differently from typing text in
+Insert mode. It doesn't allow many commands to change the text. For most
+commands that's OK, but sometimes you have to type a complicated command.
+That's where the command line window is useful.
Open the command line window with this command: >
diff --git a/runtime/doc/usr_30.txt b/runtime/doc/usr_30.txt
index 736323665e..bcb7b59e74 100644
--- a/runtime/doc/usr_30.txt
+++ b/runtime/doc/usr_30.txt
@@ -336,7 +336,7 @@ How to do that is explained here: |indent-expression|.
==============================================================================
*30.4* Other indenting
-The most simple form of automatic indenting is with the 'autoindent' option.
+The simplest form of automatic indenting is with the 'autoindent' option.
It uses the indent from the previous line. A bit smarter is the 'smartindent'
option. This is useful for languages where no indent file is available.
'smartindent' is not as smart as 'cindent', but smarter than 'autoindent'.
diff --git a/runtime/doc/usr_31.txt b/runtime/doc/usr_31.txt
index 0794b3aa80..afbc91877c 100644
--- a/runtime/doc/usr_31.txt
+++ b/runtime/doc/usr_31.txt
@@ -1,4 +1,4 @@
-*usr_31.txt* For Vim version 8.2. Last change: 2007 May 08
+*usr_31.txt* For Vim version 8.2. Last change: 2020 Jul 28
VIM USER MANUAL - by Bram Moolenaar
@@ -198,9 +198,9 @@ is not possible in most terminals.
You can start the X-Windows version of gvim with an argument to specify the