mirror of
https://github.com/neovim/neovim.git
synced 2025-09-10 05:18:16 +00:00
vim-patch:88774f
Updated runtime files and Italian messages.
88774fdd23
This commit is contained in:
@@ -1,4 +1,4 @@
|
|||||||
*autocmd.txt* For Vim version 7.4. Last change: 2015 Aug 05
|
*autocmd.txt* For Vim version 7.4. Last change: 2015 Aug 18
|
||||||
|
|
||||||
|
|
||||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||||
@@ -1100,7 +1100,7 @@ Instead of a pattern buffer-local autocommands use one of these forms:
|
|||||||
Examples: >
|
Examples: >
|
||||||
:au CursorHold <buffer> echo 'hold'
|
:au CursorHold <buffer> echo 'hold'
|
||||||
:au CursorHold <buffer=33> echo 'hold'
|
:au CursorHold <buffer=33> echo 'hold'
|
||||||
:au BufNewFile * CursorHold <buffer=abuf> echo 'hold'
|
:au BufNewFile * au CursorHold <buffer=abuf> echo 'hold'
|
||||||
|
|
||||||
All the commands for autocommands also work with buffer-local autocommands,
|
All the commands for autocommands also work with buffer-local autocommands,
|
||||||
simply use the special string instead of the pattern. Examples: >
|
simply use the special string instead of the pattern. Examples: >
|
||||||
|
@@ -1,4 +1,4 @@
|
|||||||
*editing.txt* For Vim version 7.4. Last change: 2015 Jul 28
|
*editing.txt* For Vim version 7.4. Last change: 2015 Aug 25
|
||||||
|
|
||||||
|
|
||||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||||
@@ -381,6 +381,7 @@ Finds files:
|
|||||||
On Unix and a few other systems you can also use backticks for the file name
|
On Unix and a few other systems you can also use backticks for the file name
|
||||||
argument, for example: >
|
argument, for example: >
|
||||||
:next `find . -name ver\\*.c -print`
|
:next `find . -name ver\\*.c -print`
|
||||||
|
:view `ls -t *.patch \| head -n1`
|
||||||
The backslashes before the star are required to prevent the shell from
|
The backslashes before the star are required to prevent the shell from
|
||||||
expanding "ver*.c" prior to execution of the find program. The backslash
|
expanding "ver*.c" prior to execution of the find program. The backslash
|
||||||
before the shell pipe symbol "|" prevents Vim from parsing it as command
|
before the shell pipe symbol "|" prevents Vim from parsing it as command
|
||||||
@@ -398,13 +399,11 @@ The expression can contain just about anything, thus this can also be used to
|
|||||||
avoid the special meaning of '"', '|', '%' and '#'. However, 'wildignore'
|
avoid the special meaning of '"', '|', '%' and '#'. However, 'wildignore'
|
||||||
does apply like to other wildcards.
|
does apply like to other wildcards.
|
||||||
|
|
||||||
Environment variables are expanded before evaluating the expression, thus this
|
Environment variables in the expression are expanded when evaluating the
|
||||||
does not work: >
|
expression, thus this works: >
|
||||||
:e `=$HOME . '.vimrc'`
|
:e `=$HOME . '/.vimrc'`
|
||||||
Because $HOME is expanding early, resulting in: >
|
This does not work, $HOME is inside a string and used literally: >
|
||||||
:e `=/home/user . '.vimrc'`
|
:e `='$HOME' . '/.vimrc'`
|
||||||
This does work: >
|
|
||||||
:e `=expand('$HOME') . '.vimrc'`
|
|
||||||
|
|
||||||
If the expression returns a string then names are to be separated with line
|
If the expression returns a string then names are to be separated with line
|
||||||
breaks. When the result is a |List| then each item is used as a name. Line
|
breaks. When the result is a |List| then each item is used as a name. Line
|
||||||
|
@@ -49,9 +49,12 @@ achieve special effects. These options come in three forms:
|
|||||||
:se[t] {option}&vi Reset option to its Vi default value.
|
:se[t] {option}&vi Reset option to its Vi default value.
|
||||||
:se[t] {option}&vim Reset option to its Vim default value.
|
:se[t] {option}&vim Reset option to its Vim default value.
|
||||||
|
|
||||||
:se[t] all& Set all options, except terminal options, to their
|
:se[t] all& Set all options to their default value. The values of
|
||||||
default value. The values of 'lines' and 'columns'
|
these options are not changed:
|
||||||
are not changed.
|
'columns'
|
||||||
|
'encoding'
|
||||||
|
'lines'
|
||||||
|
Warning: This may have a lot of side effects.
|
||||||
|
|
||||||
*:set-args* *E487* *E521*
|
*:set-args* *E487* *E521*
|
||||||
:se[t] {option}={value} or
|
:se[t] {option}={value} or
|
||||||
|
@@ -1,4 +1,4 @@
|
|||||||
*syntax.txt* For Vim version 7.4. Last change: 2015 Jul 21
|
*syntax.txt* For Vim version 7.4. Last change: 2015 Aug 13
|
||||||
|
|
||||||
|
|
||||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||||
@@ -3430,7 +3430,7 @@ DEFINING KEYWORDS *:syn-keyword*
|
|||||||
:syntax keyword Type contained int long char
|
:syntax keyword Type contained int long char
|
||||||
:syntax keyword Type int long contained char
|
:syntax keyword Type int long contained char
|
||||||
:syntax keyword Type int long char contained
|
:syntax keyword Type int long char contained
|
||||||
< *E789*
|
< *E789* *E890*
|
||||||
When you have a keyword with an optional tail, like Ex commands in
|
When you have a keyword with an optional tail, like Ex commands in
|
||||||
Vim, you can put the optional characters inside [], to define all the
|
Vim, you can put the optional characters inside [], to define all the
|
||||||
variations at once: >
|
variations at once: >
|
||||||
|
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user