forked from aniani/vim
Update runtime files
This commit is contained in:
Bram Moolenaar
@@ -1,4 +1,4 @@
|
||||
*autocmd.txt* For Vim version 8.1. Last change: 2018 May 03
|
||||
*autocmd.txt* For Vim version 8.1. Last change: 2018 Dec 28
|
||||
|
||||
|
||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||
@@ -759,13 +759,14 @@ FilterReadPre Before reading a file from a filter command.
|
||||
Not triggered when 'shelltemp' is off.
|
||||
*FilterWritePost*
|
||||
FilterWritePost After writing a file for a filter command or
|
||||
making a diff.
|
||||
making a diff with an external diff (see
|
||||
DiffUpdated for internal diff).
|
||||
Vim checks the pattern against the name of
|
||||
the current buffer as with FilterWritePre.
|
||||
Not triggered when 'shelltemp' is off.
|
||||
*FilterWritePre*
|
||||
FilterWritePre Before writing a file for a filter command or
|
||||
making a diff.
|
||||
making a diff with an external diff.
|
||||
Vim checks the pattern against the name of
|
||||
the current buffer, not the name of the
|
||||
temporary file that is the output of the
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
*eval.txt* For Vim version 8.1. Last change: 2018 Dec 27
|
||||
*eval.txt* For Vim version 8.1. Last change: 2018 Dec 28
|
||||
|
||||
|
||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||
@@ -6773,7 +6773,8 @@ prop_list({lnum} [, {props}]) *prop_list()*
|
||||
The properties are ordered by starting column and priority.
|
||||
Each property is a Dict with these entries:
|
||||
col starting column
|
||||
length length in bytes
|
||||
length length in bytes, one more if line break is
|
||||
included
|
||||
id property ID
|
||||
type name of the property type, omitted if
|
||||
the type was deleted
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
*help.txt* For Vim version 8.1. Last change: 2018 Dec 14
|
||||
*help.txt* For Vim version 8.1. Last change: 2019 Jan 01
|
||||
|
||||
VIM - main help file
|
||||
k
|
||||
@@ -10,7 +10,7 @@ Close this window: Use ":q<Enter>".
|
||||
Jump to a subject: Position the cursor on a tag (e.g. |bars|) and hit CTRL-].
|
||||
With the mouse: ":set mouse=a" to enable the mouse (in xterm or GUI).
|
||||
Double-click the left mouse button on a tag, e.g. |bars|.
|
||||
Jump back: Type CTRL-T or CTRL-O. Repeat to go further back.
|
||||
Jump back: Type CTRL-O. Repeat to go further back.
|
||||
|
||||
Get specific help: It is possible to go directly to whatever you want help
|
||||
on, by giving an argument to the |:help| command.
|
||||
@@ -31,13 +31,17 @@ Get specific help: It is possible to go directly to whatever you want help
|
||||
help entries for "word".
|
||||
Or use ":helpgrep word". |:helpgrep|
|
||||
|
||||
Getting started: Do the Vim tutor, a 20 minute interactive training for the
|
||||
basic commands, see |vimtutor|.
|
||||
Read the user manual from start to end: |usr_01.txt|
|
||||
|
||||
Vim stands for Vi IMproved. Most of Vim was made by Bram Moolenaar, but only
|
||||
through the help of many others. See |credits|.
|
||||
------------------------------------------------------------------------------
|
||||
*doc-file-list* *Q_ct*
|
||||
BASIC:
|
||||
|quickref| Overview of the most common commands you will use
|
||||
|tutor| 30 minutes training course for beginners
|
||||
|tutor| 20 minutes training course for beginners
|
||||
|copying| About copyrights
|
||||
|iccf| Helping poor children in Uganda
|
||||
|sponsor| Sponsor Vim development, become a registered Vim user
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
*intro.txt* For Vim version 8.1. Last change: 2018 Jan 24
|
||||
*intro.txt* For Vim version 8.1. Last change: 2019 Jan 01
|
||||
|
||||
|
||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||
@@ -52,29 +52,11 @@ an introduction to the use of Vi or Vim, it gets a bit complicated here and
|
||||
there. For beginners, there is a hands-on |tutor|. To learn using Vim, read
|
||||
the user manual |usr_toc.txt|.
|
||||
|
||||
*book*
|
||||
There are many books on Vi that contain a section for beginners. There are
|
||||
two books I can recommend:
|
||||
|
||||
"Vim - Vi Improved" by Steve Oualline
|
||||
|
||||
This is the very first book completely dedicated to Vim. It is very good for
|
||||
beginners. The most often used commands are explained with pictures and
|
||||
examples. The less often used commands are also explained, the more advanced
|
||||
features are summarized. There is a comprehensive index and a quick
|
||||
reference. Parts of this book have been included in the user manual
|
||||
|frombook|.
|
||||
Published by New Riders Publishing. ISBN: 0735710015
|
||||
For more information try one of these:
|
||||
http://iccf-holland.org/click5.html
|
||||
http://www.vim.org/iccf/click5.html
|
||||
|
||||
"Learning the Vi editor" by Linda Lamb and Arnold Robbins
|
||||
|
||||
This is a book about Vi that includes a chapter on Vim (in the sixth edition).
|
||||
The first steps in Vi are explained very well. The commands that Vim adds are
|
||||
only briefly mentioned. There is also a German translation.
|
||||
Published by O'Reilly. ISBN: 1-56592-426-6.
|
||||
*book* *books*
|
||||
Most books on Vi and Vim contain a section for beginners. Others are spending
|
||||
more words on specific functionality. You can find an overview of Vim books
|
||||
here:
|
||||
http://iccf-holland.org/vim_books.html
|
||||
|
||||
==============================================================================
|
||||
2. Vim on the internet *internet*
|
||||
@@ -84,9 +66,9 @@ The Vim pages contain the most recent information about Vim. They also
|
||||
contain links to the most recent version of Vim. The FAQ is a list of
|
||||
Frequently Asked Questions. Read this if you have problems.
|
||||
|
||||
Vim home page: http://www.vim.org/
|
||||
Vim FAQ: http://vimdoc.sf.net/
|
||||
Downloading: ftp://ftp.vim.org/pub/vim/MIRRORS
|
||||
Vim home page: https://www.vim.org/
|
||||
Vim FAQ: https://vimhelp.appspot.com/vim_faq.txt.html
|
||||
Downloading: https://www.vim.org/download.php
|
||||
|
||||
|
||||
Usenet News group where Vim is discussed: *news* *usenet*
|
||||
@@ -114,10 +96,12 @@ There are several mailing lists for Vim:
|
||||
See http://www.vim.org/maillist.php for the latest information.
|
||||
|
||||
NOTE:
|
||||
- Anyone can see the archive, e.g. on Google groups. Search this if you have
|
||||
questions.
|
||||
- You can only send messages to these lists if you have subscribed!
|
||||
- The first message is moderated, thus it may take a few hours to show up.
|
||||
- You need to send the messages from the same location as where you subscribed
|
||||
from (to avoid spam mail).
|
||||
- Maximum message size is 40000 characters.
|
||||
|
||||
*subscribe-maillist*
|
||||
If you want to join, send a message to
|
||||
@@ -150,7 +134,10 @@ Preferably start Vim with: >
|
||||
Where reproduce.vim is a script that reproduces the problem. Try different
|
||||
machines, if relevant (is this an MS-Windows specific bug perhaps?).
|
||||
|
||||
Send me patches if you can!
|
||||
Send me patches if you can! If you create a pull request on
|
||||
https://github.com/vim/vim then the automated checks will run and report any
|
||||
obvious problems. But you can also send the patch by email (use an attachment
|
||||
to avoid white space changes).
|
||||
|
||||
It will help to include information about the version of Vim you are using and
|
||||
your setup. You can get the information with this command: >
|
||||
@@ -189,7 +176,7 @@ introduce Y2K problems, but those are not really part of Vim itself.
|
||||
==============================================================================
|
||||
3. Credits *credits* *author* *Bram* *Moolenaar*
|
||||
|
||||
Most of Vim was written by Bram Moolenaar <Bram@vim.org>.
|
||||
Most of Vim was created by Bram Moolenaar <Bram@vim.org>.
|
||||
|
||||
Parts of the documentation come from several Vi manuals, written by:
|
||||
W.N. Joy
|
||||
@@ -268,6 +255,7 @@ Vim would never have become what it is now, without the help of these people!
|
||||
Ken Takata fixes and features
|
||||
Kazunobu Kuriyama GTK 3
|
||||
Christian Brabandt many fixes, features, user support, etc.
|
||||
Yegappan Lakshmanan many quickfix features
|
||||
|
||||
I wish to thank all the people that sent me bug reports and suggestions. The
|
||||
list is too long to mention them all here. Vim would not be the same without
|
||||
@@ -300,6 +288,12 @@ Elvis Another Vi clone, made by Steve Kirkendall. Very compact but isn't
|
||||
as flexible as Vim.
|
||||
The version used is 2.1. It is still being developed. Source code is
|
||||
freely available.
|
||||
*NeoVim*
|
||||
NeoVim A Vim clone. Forked the Vim source in 2014 and went a different way.
|
||||
Very much bound to github and has many more dependencies, making
|
||||
development more complex and limiting portability. Code has been
|
||||
refactored, resulting in patches not being exchangeable with Vim.
|
||||
Supports a remote GUI and integration with scripting languages.
|
||||
|
||||
==============================================================================
|
||||
4. Notation *notation*
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
*message.txt* For Vim version 8.1. Last change: 2018 Feb 04
|
||||
*message.txt* For Vim version 8.1. Last change: 2018 Dec 30
|
||||
|
||||
|
||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||
@@ -557,14 +557,6 @@ This message is only given when Vim detects a problem when searching for a
|
||||
tag. Sometimes this message is not given, even though the tags file is not
|
||||
properly sorted.
|
||||
|
||||
*E460* >
|
||||
The resource fork would be lost (add ! to override)
|
||||
|
||||
On the Macintosh (classic), when writing a file, Vim attempts to preserve all
|
||||
info about a file, including its resource fork. If this is not possible you
|
||||
get this error message. Append "!" to the command name to write anyway (and
|
||||
lose the info).
|
||||
|
||||
*E424* >
|
||||
Too many different highlighting attributes in use
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
*sign.txt* For Vim version 8.1. Last change: 2018 Dec 26
|
||||
*sign.txt* For Vim version 8.1. Last change: 2019 Jan 01
|
||||
|
||||
|
||||
VIM REFERENCE MANUAL by Gordon Prieur
|
||||
@@ -88,7 +88,7 @@ See |sign_define()| for the equivalent Vim script function.
|
||||
:sign define {name} {argument}...
|
||||
Define a new sign or set attributes for an existing sign.
|
||||
The {name} can either be a number (all digits) or a name
|
||||
starting with a non-digit. Leading digits are ignored, thus
|
||||
starting with a non-digit. Leading zeros are ignored, thus
|
||||
"0012", "012" and "12" are considered the same name.
|
||||
About 120 different signs can be defined.
|
||||
|
||||
|
||||
@@ -2702,9 +2702,29 @@ later, and part earlier) adds.
|
||||
|
||||
RESTRUCTURED TEXT *rst.vim* *ft-rst-syntax*
|
||||
|
||||
You may set what syntax definitions should be used for code blocks via >
|
||||
Syntax highlighting is enabled for code blocks within the document for a
|
||||
select number of file types. See $VIMRUNTIME/syntax/rst.vim for the default
|
||||
syntax list.
|
||||
|
||||
To set a user-defined list of code block syntax highlighting: >
|
||||
let rst_syntax_code_list = ['vim', 'lisp', ...]
|
||||
<
|
||||
|
||||
To assign multiple code block types to a single syntax, define
|
||||
`rst_syntax_code_list` as a mapping: >
|
||||
let rst_syntax_code_list = {
|
||||
\ 'cpp' = ['cpp', 'c++'],
|
||||
\ 'bash' = ['bash', 'sh'],
|
||||
...
|
||||
}
|
||||
|
||||
To use color highlighting for emphasis text: >
|
||||
let rst_use_emphasis_colors = 1
|
||||
|
||||
To enable folding of sections: >
|
||||
let rst_fold_enabled = 1
|
||||
|
||||
Note that folding can cause performance issues on some platforms.
|
||||
|
||||
|
||||
REXX *rexx.vim* *ft-rexx-syntax*
|
||||
|
||||
|
||||
@@ -4128,7 +4128,6 @@ E457 print.txt /*E457*
|
||||
E458 message.txt /*E458*
|
||||
E459 message.txt /*E459*
|
||||
E46 message.txt /*E46*
|
||||
E460 message.txt /*E460*
|
||||
E461 eval.txt /*E461*
|
||||
E462 editing.txt /*E462*
|
||||
E463 netbeans.txt /*E463*
|
||||
@@ -4770,6 +4769,7 @@ N: cmdline.txt /*N:*
|
||||
N<Del> various.txt /*N<Del>*
|
||||
NFA pattern.txt /*NFA*
|
||||
NL-used-for-Nul pattern.txt /*NL-used-for-Nul*
|
||||
NeoVim intro.txt /*NeoVim*
|
||||
NetBSD-backspace options.txt /*NetBSD-backspace*
|
||||
NetUserPass() pi_netrw.txt /*NetUserPass()*
|
||||
Normal intro.txt /*Normal*
|
||||
@@ -5291,6 +5291,7 @@ bold syntax.txt /*bold*
|
||||
bom-bytes mbyte.txt /*bom-bytes*
|
||||
book intro.txt /*book*
|
||||
bookmark usr_03.txt /*bookmark*
|
||||
books intro.txt /*books*
|
||||
boolean options.txt /*boolean*
|
||||
break-finally eval.txt /*break-finally*
|
||||
browse() eval.txt /*browse()*
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
*textprop.txt* For Vim version 8.1. Last change: 2018 Dec 27
|
||||
*textprop.txt* For Vim version 8.1. Last change: 2018 Dec 30
|
||||
|
||||
|
||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||
@@ -70,11 +70,14 @@ Suppose line 11 in a buffer has this text (excluding the indent):
|
||||
|
||||
The number 123 is smaller than 4567.
|
||||
|
||||
To highlight the numbers: >
|
||||
To highlight the numbers in this text: >
|
||||
call prop_type_add('number', {'highlight': 'Constant'})
|
||||
call prop_add(11, 12, {'length': 3, 'type': 'number'})
|
||||
call prop_add(11, 32, {'length': 4, 'type': 'number'})
|
||||
|
||||
Try inserting or deleting lines above the text, you will see that the text
|
||||
properties stick to the text, thus the line number is adjusted as needed.
|
||||
|
||||
Setting "start_incl" and "end_incl" is useful when white space surrounds the
|
||||
text, e.g. for a function name. Using false is useful when the text starts
|
||||
and/or ends with a specific character, such as the quote surrounding a string.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
*todo.txt* For Vim version 8.1. Last change: 2018 Dec 27
|
||||
*todo.txt* For Vim version 8.1. Last change: 2019 Jan 01
|
||||
|
||||
|
||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||
@@ -38,6 +38,9 @@ browser use: https://github.com/vim/vim/issues/1234
|
||||
*known-bugs*
|
||||
-------------------- Known bugs and current work -----------------------
|
||||
|
||||
Valgrind error in old regexp engine when using TOhtml.
|
||||
(Dominique, 2018 Dec 31, #3749)
|
||||
|
||||
Possible errors reported from fuzzer. Shadowblade #3716
|
||||
a) using get_regline() without checking for NULL
|
||||
b) using getcell() in libvterm without checking for NULL
|
||||
@@ -149,6 +152,9 @@ Improve fallback for menu translations, to avoid having to create lots of
|
||||
files that source the actual file. E.g. menu_da_de -> menu_da
|
||||
Include part of #3242?
|
||||
|
||||
Patch to add 'p' flag to 'formatoptions'. (Tom Ryder, 2018 Dec 28)
|
||||
Wait a few days for feedback.
|
||||
|
||||
When a terminal exit_cb closes the window, a following typed key is lost, if
|
||||
it's in a mapping. (2018 Oct 6, #2302, #3522)
|
||||
|
||||
@@ -223,6 +229,9 @@ When 'sidescrolloff' is set, using "zl" to go to the end of the line, suddenly
|
||||
scrolls back. Should allow for this scrolling, like 'scrolloff' does when
|
||||
using CTRL-E. (Yee Cheng Chin, #3721)
|
||||
|
||||
We have a SourcePre autocommand event, but not SourcePost. Useful for doing
|
||||
some thing after a plugin was loaded. (#3739)
|
||||
|
||||
Invalid memory access with old regexp engine. (Dominique Pelle, 2018 Sep 3,
|
||||
#3405) Introduced by 8.0.1517, which was fixing another memory access error.
|
||||
(Sep 8)
|
||||
|
||||
Reference in New Issue
Block a user