1
0
forked from aniani/vim

updated for version 7.1a

This commit is contained in:
Bram Moolenaar
2007-05-05 18:24:42 +00:00
parent 9aae141a6b
commit c81e5e79a0
131 changed files with 9107 additions and 2709 deletions

515
runtime/doc/ada.txt Normal file
View File

@@ -0,0 +1,515 @@
*ada.txt* For Vim version 7.1a. Last change: 2006 Nov 12
ADA FILE TYPE PLUG-INS REFERENCE MANUAL~
ADA *ada.vim*
1. Syntax Highlighting |ft-ada-syntax|
2. Plug-in |ft-ada-plugin|
3. Omni Completion |ft-ada-omni|
3.1 Omni Completion with "gnat xref" |gnat-xref|
3.2 Omni Completion with "ctags" |ada-ctags|
4. Compiler Support |ada-compiler|
4.1 GNAT |compiler-gnat|
4.1 Dec Ada |compiler-decada|
5. References |ada-reference|
5.1 Options |ft-ada-options|
5.2 Functions |ft-ada-functions|
5.3 Commands |ft-ada-commands|
5.4 Variables |ft-ada-variables|
5.5 Constants |ft-ada-constants|
8. Extra Plug-ins |ada-extra-plugins|
==============================================================================
1. Syntax Highlighting ~
*ft-ada-syntax*
This mode is designed for the 2005 edition of Ada ("Ada 2005"), which includes
support for objected-programming, protected types, and so on. It handles code
written for the original Ada language ("Ada83", "Ada87", "Ada95") as well,
though code which uses Ada 2005-only keywords will be wrongly colored (such
code should be fixed anyway). For more information about Ada, see
http://www.adapower.com.
The Ada mode handles a number of situations cleanly.
For example, it knows that the "-" in "-5" is a number, but the same character
in "A-5" is an operator. Normally, a "with" or "use" clause referencing
another compilation unit is coloured the same way as C's "#include" is coloured.
If you have "Conditional" or "Repeat" groups coloured differently, then "end
if" and "end loop" will be coloured as part of those respective groups.
You can set these to different colours using vim's "highlight" command (e.g.,
to change how loops are displayed, enter the command ":hi Repeat" followed by
the colour specification; on simple terminals the colour specification
ctermfg=White often shows well).
There are several options you can select in this Ada mode. See|ft-ada-options|
for a complete list.
To enable them, assign a value to the option. For example, to turn one on:
>
> let g:ada_standard_types = 1
>
To disable them use ":unlet". Example:
>
> unlet g:ada_standard_types
You can just use ":" and type these into the command line to set these
temporarily before loading an Ada file. You can make these option settings
permanent by adding the "let" command(s), without a colon, to your "~/.vimrc"
file.
Even on a slow (90Mhz) PC this mode works quickly, but if you find the
performance unacceptable, turn on |g:ada_withuse_ordinary|.
Syntax folding instructions (|fold-syntax|) are added when |g:ada_folding| is
set.
==============================================================================
2. File type Plug-in ~
*ft-ada-indent* *ft-ada-plugin*
The Ada plug-in provides support for:
- auto indenting (|indent.txt|)
- insert completion (|i_CTRL-N|)
- user completion (|i_CTRL-X_CTRL-U|)
- tag searches (|tagsrch.txt|)
- Quick Fix (|quickfix.txt|)
- backspace handling (|'backspace'|)
- comment handling (|'comments'|, |'commentstring'|)
The plug-in only activates the features of the Ada mode whenever an Ada
files is opened and add adds Ada related entries to the main and pop-up menu.
==============================================================================
3. Omni Completion ~
*ft-ada-omni*
The Ada omni-completions (|i_CTRL-X_CTRL-O|) uses tags database created either
by "gnat xref -v" or the "exuberant Ctags (http://ctags.sourceforge.net). The
complete function will automatically detect which tool was used to create the
tags file.
------------------------------------------------------------------------------
3.1 Omni Completion with "gnat xref" ~
*gnat-xref*
GNAT XREF uses the compiler internal informations (ali-files) to produce the
tags file. This has the advantage to be 100% correct and the option of deep
nested analysis. However the code must compile, the generator is quite
slow and the created tags file contains only the basic Ctags informations for
each entry - not enough for some of the more advanced Vim code browser
plug-ins.
NOTE: "gnat xref -v" is very tricky to use as it has almost no diagnostic
output - If nothing is printed then usually the parameters are wrong.
Here some important tips:
1) You need to compile your code first and use the "-aO" option to point to
your .ali files.
2) "gnat xref -v ../Include/adacl.ads" won't work - use the "gnat xref -v
-aI../Include adacl.ads" instead.
3) "gnat xref -v -aI../Include *.ad?" won't work - use "cd ../Include" and
then "gnat xref -v *.ad?"
4) Project manager support is completely broken - don't even try "gnat xref
-Padacl.gpr".
5) VIM is faster when the tags file is sorted - use "sort --unique
--ignore-case --output=tags tags" .
6) Remember to insert "!_TAG_FILE_SORTED 2 %sort ui" as first line to mark
the file assorted.
------------------------------------------------------------------------------
3.2 Omni Completion with "ctags"~
*ada-ctags*
Exuberant Ctags uses it's own multi-language code parser. The parser is quite
fast, produces a lot of extra informations (hence the name "Exuberant Ctags")
and can run on files which currently do not compile.
There are also lots of other Vim-tools which use exuberant Ctags.
You will need to install a version of the Exuberant Ctags which has Ada
support patched in. Such a version is available from the GNU Ada Project
(http://gnuada.sourceforge.net).
The Ada parser for Exuberant Ctags is fairly new - don't expect complete
support yet.
==============================================================================
4. Compiler Support ~
*ada-compiler*
The Ada mode supports more then one Ada compiler and will automatically load the
compiler set in|g:ada_default_compiler|whenever an Ada source is opened. The
provided compiler plug-ins are split into the actual compiler plug-in and a
collection of support functions and variables. This allows the easy
development of specialized compiler plug-ins fine tuned to your development
environment.
------------------------------------------------------------------------------
4.1 GNAT ~
*compiler-gnat*
GNAT is the only free (beer and speech) Ada compiler available. There are
several version available which differentiate in the licence terms used.
The GNAT compiler plug-in will perform a compile on pressing <F7> and then
immediately shows the result. You can set the project file to be used by
setting:
>
> call g:gnat.Set_Project_File ('my_project.gpr')
Setting a project file will also create a Vim session (|views-sessions|) so -
like with the GPS - opened files, window positions etc. will remembered
separately for all projects.
*gnat_members*
GNAT OBJECT ~
*g:gnat.Make()*
g:gnat.Make()
Calls|g:gnat.Make_Command|and displays the result inside a
|quickfix| window.
*g:gnat.Pretty()*
g:gnat.Pretty()
Calls|g:gnat.Pretty_Command|
*g:gnat.Find()*
g:gnat.Find()
Calls|g:gnat.Find_Command|
*g:gnat.Tags()*
g:gnat.Tags()
Calls|g:gnat.Tags_Command|
*g:gnat.Set_Project_File()*
g:gnat.Set_Project_File([{file}])
Set gnat project file and load associated session. An open
project will be closed and the session written. If called
without file name the file selector opens for selection of a
project file. If called with an empty string then the project
and associated session are closed.
*g:gnat.Project_File*
g:gnat.Project_File string
Current project file.
*g:gnat.Make_Command*
g:gnat.Make_Command string
External command used for|g:gnat.Make()| (|'makeprg'|).
*g:gnat.Pretty_Program*
g:gnat.Pretty_Program string
External command used for|g:gnat.Pretty()|
*g:gnat.Find_Program*
g:gnat.Find_Program string
External command used for|g:gnat.Find()|
*g:gnat.Tags_Command*
g:gnat.Tags_Command string
External command used for|g:gnat.Tags()|
*g:gnat.Error_Format*
g:gnat.Error_Format string
Error format (|'errorformat'|)
------------------------------------------------------------------------------
4.2 Dec Ada ~
*compiler-hpada* *compiler-decada*
*compiler-vaxada* *compiler-compaqada*
Dec Ada (also known by - in chronological order - VAX Ada, Dec Ada, Compaq Ada
and HP Ada) is a fairly dated Ada 83 compiler. Support is basic: <F7> will
compile the current unit.
The Dec Ada compiler expects the package name and not the file name to be
passed a parameter. The compiler plug-in supports the usual file name
convention to convert the file into a unit name. For separates both '-' and
'__' are allowed.
*decada_members*
DEC ADA OBJECT ~
*g:decada.Make()*
g:decada.Make() function
Calls|g:decada.Make_Command|and displays the result inside a
|quickfix| window.
*g:decada.Unit_Name()*
g:decada.Unit_Name() function
Get the Unit name for the current file.
*g:decada.Make_Command*
g:decada.Make_Command string
External command used for|g:decadat.Make()| (|'makeprg'|).
*g:decada.Error_Format*
g:decada.Error_Format| string
Error format (|'errorformat'|).
==============================================================================
5. References ~
*ada-reference*
------------------------------------------------------------------------------
5.1 Options ~
*ft-ada-options*
*g:ada_standard_types*
g:ada_standard_types bool (true when exists)
Highlight types in package Standard (e.g., "Float")
*g:ada_space_errors*
*g:ada_no_trail_space_error*
*g:ada_no_tab_space_error*
*g:ada_all_tab_usage*
g:ada_space_errors bool (true when exists)
Highlight extraneous errors in spaces ...
g:ada_no_trail_space_error
- but ignore trailing spaces at the end of a line
g:ada_no_tab_space_error
- but ignore tabs after spaces
g:ada_all_tab_usage
- highlight all tab use
*g:ada_line_errors*
g:ada_line_errors bool (true when exists)
Highlight lines which are to long. Note: This highlighting
option is quite CPU intensive.
*g:ada_rainbow_color*
g:ada_rainbow_color bool (true when exists)
Use rainbow colours for '(' and ')'. You need the
rainbow_parenthesis for this to work
*g:ada_folding*
g:ada_folding set ('sigpft')
Use folding for Ada sources.
's': activate syntax folding on load
'p': fold packages
'f': fold functions and procedures
't': fold types
'c': fold conditionals
'g': activate gnat pretty print folding on load
'i': lone 'is' folded with line above
'b': lone 'begin' folded with line above
'p': lone 'private' folded with line above
'x': lone 'exception' folded with line above
'i': activate indent folding on load
Note: Syntax folding is in an early (unuseable) stage and
indent or gnat pretty folding is suggested.
For gnat pretty folding to work the following settings are
suggested: -cl3 -M79 -c2 -c3 -c4 -A1 -A2 -A3 -A4 -A5
For indent folding to work the following settings are
suggested: shiftwidth=3 softtabstop=3
*g:ada_abbrev*
g:ada_abbrev bool (true when exists)
Add some abbreviations. This feature more or less superseded
by the various completion methods.
*g:ada_withuse_ordinary*
g:ada_withuse_ordinary bool (true when exists)
Show "with" and "use" as ordinary keywords (when used to
reference other compilation units they're normally highlighted
specially).
*g:ada_begin_preproc*
g:ada_begin_preproc bool (true when exists)
Show all begin-like keywords using the colouring of C
preprocessor commands.
*g:ada_omni_with_keywords*
g:ada_omni_with_keywords
Add Keywords, Pragmas, Attributes to omni-completions
(|compl-omni|). Note: You can always complete then with user
completion (|i_CTRL-X_CTRL-U|).
*g:ada_extended_tagging*
g:ada_extended_tagging enum ('jump', 'list')
use extended tagging, two options are available
'jump': use tjump to jump.
'list': add tags quick fix list.
Normal tagging does not support function or operator
overloading as these features are not available in C and
tagging was originally developed for C.
*g:ada_extended_completion*
g:ada_extended_completion
Uses extended completion for <C-N> and <C-R> completions
(|i_CTRL-N|). In this mode the '.' is used as part of the
identifier so that 'Object.Method' or 'Package.Procedure' are
completed together.
*g:ada_gnat_extensions*
g:ada_gnat_extensions bool (true when exists)
Support GNAT extensions.
*g:ada_with_gnat_project_files*
g:ada_with_gnat_project_files bool (true when exists)
Add gnat project file keywords and Attributes.
*g:ada_default_compiler*
g:ada_default_compiler string
set default compiler. Currently supported is 'gnat' and
'decada'.
An "exists" type is a boolean is considered true when the variable is defined
and false when the variable is undefined. The value which the variable is
set makes no difference.
------------------------------------------------------------------------------
5.3 Commands ~
*ft-ada-commands*
:AdaRainbow *:AdaRainbow*
Toggles rainbow colour (|g:ada_rainbow_color|) mode for
'(' and ')'
:AdaLines *:AdaLines*
Toggles line error (|g:ada_line_errors|) display
:AdaSpaces *:AdaSpaces*
Toggles space error (|g:ada_space_errors|) display.
:AdaTagDir *:AdaTagDir*
Creates tags file for the directory of the current file.
:AdaTagFile *:AdaTagFile*
Creates tags file for the current file.
:AdaTypes *:AdaTypes*
Toggles standard types (|g:ada_standard_types|) colour.
:GnatFind *:GnatFind*
Calls |g:gnat.Find()|
:GnatPretty *:GnatPretty*
Calls |g:gnat.Pretty()|
:GnatTags *:GnatTags*
Calls |g:gnat.Tags()|
------------------------------------------------------------------------------
5.3 Variables ~
*ft-ada-variables*
*g:gnat*
g:gnat object
Control object which manages GNAT compiles. The object
is created when the first Ada source code is loaded provided
that |g:ada_default_compiler|is set to 'gnat'. See|gnat_members|
for details.
*g:decada*
g:decada object
Control object which manages Dec Ada compiles. The object
is created when the first Ada source code is loaded provided
that |g:ada_default_compiler|is set to 'decada'. See
|decada_members|for details.
------------------------------------------------------------------------------
5.4 Constants ~
*ft-ada-constants*
All constants are locked. See |:lockvar| for details.
*g:ada#WordRegex*
g:ada#WordRegex string
Regular expression to search for Ada words
*g:ada#DotWordRegex*
g:ada#DotWordRegex string
Regular expression to search for Ada words separated by dots.
*g:ada#Comment*
g:ada#Comment string
Regular expression to search for Ada comments
*g:ada#Keywords*
g:ada#Keywords list of dictionaries
List of keywords, attributes etc. pp. in the format used by
omni completion. See |complete-items| for details.
*g:ada#Ctags_Kinds*
g:ada#Ctags_Kinds dictionary of lists
Dictionary of the various kinds of items which the Ada support
for Ctags generates.
------------------------------------------------------------------------------
5.2 Functions ~
*ft-ada-functions*
ada#Word([{line}, {col}]) *ada#Word()*
Return full name of Ada entity under the cursor (or at given
line/column), stripping white space/newlines as necessary.
ada#List_Tag([{line}, {col}]) *ada#Listtags()*
List all occurrences of the Ada entity under the cursor (or at
given line/column) inside the quick-fix window
ada#Jump_Tag ({ident}, {mode}) *ada#Jump_Tag()*
List all occurrences of the Ada entity under the cursor (or at
given line/column) in the tag jump list. Mode can either be
'tjump' or 'stjump'.
ada#Create_Tags ({option}) *ada#Create_Tags()*
Creates tag file using Ctags. The option can either be 'file'
for the current file, 'dir' for the directory of the current
file or a file name.
gnat#Insert_Tags_Header() *gnat#Insert_Tags_Header()*
Adds the tag file header (!_TAG_) informations to the current
file which are missing from the GNAT XREF output.
ada#Switch_Syntax_Option ({option}) *ada#Switch_Syntax_Option()*
Toggles highlighting options on or off. Used for the Ada menu.
*gnat#New()*
gnat#New ()
Create a new gnat object. See |g:gnat| for details.
==============================================================================
8. Extra Plugins ~
*ada-extra-plugins*
You can optionally install the following extra plug-in. They work well with Ada
and enhance the ability of the Ada mode.:
backup.vim
http://www.vim.org/scripts/script.php?script_id=1537
Keeps as many backups as you like so you don't have to.
rainbow_parenthsis.vim
http://www.vim.org/scripts/script.php?script_id=1561
Very helpful since Ada uses only '(' and ')'.
nerd_comments.vim
http://www.vim.org/scripts/script.php?script_id=1218
Excellent commenting and uncommenting support for almost any
programming language.
matchit.vim
http://www.vim.org/scripts/script.php?script_id=39
'%' jumping for any language. The normal '%' jump only works for '{}'
style languages. The Ada mode will set the needed search patters.
taglist.vim
http://www.vim.org/scripts/script.php?script_id=273
Source code explorer sidebar. There is a patch for Ada available.
The GNU Ada Project distribution (http://gnuada.sourceforge.net) of Vim
contains all of the above.
==============================================================================
vim: textwidth=78 nowrap tabstop=8 shiftwidth=4 softtabstop=4 noexpandtab
vim: filetype=help encoding=latin1

View File

@@ -1,4 +1,4 @@
*arabic.txt* For Vim version 7.0. Last change: 2005 Mar 29
*arabic.txt* For Vim version 7.1a. Last change: 2005 Mar 29
VIM REFERENCE MANUAL by Nadim Shaikli

View File

@@ -1,4 +1,4 @@
*farsi.txt* For Vim version 7.0. Last change: 2005 Mar 29
*farsi.txt* For Vim version 7.1a. Last change: 2005 Mar 29
VIM REFERENCE MANUAL by Mortaza Ghassab Shiran

View File

@@ -1,4 +1,4 @@
*filetype.txt* For Vim version 7.0. Last change: 2006 Apr 28
*filetype.txt* For Vim version 7.1a. Last change: 2007 Mar 24
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -43,6 +43,8 @@ Detail: The ":filetype on" command will load one of these files:
BufNewFile and BufRead events. If the file type is not found by the
name, the file $VIMRUNTIME/scripts.vim is used to detect it from the
contents of the file.
When the GUI is running or will start soon, the menu.vim script is
also sourced. See |'go-M'| about avoiding that.
To add your own file types, see |new-filetype| below. To search for help on a
filetype prepend "ft-" and optionally append "-syntax", "-indent" or
@@ -304,24 +306,28 @@ all loaded. For example, if this command: >
set runtimepath
produces this output: >
produces this output:
runtimepath=/etc/vim,~/.vim,/usr/local/share/vim/vim60
runtimepath=/etc/vim,~/.vim,/usr/local/share/vim/vim60 ~
then Vim will load all plugins in these directories: >
then Vim will load all plugins in these directories and below:
/etc/vim/plugin/
~/.vim/plugin/
/usr/local/share/vim/vim60/plugin/
/etc/vim/plugin/ ~
~/.vim/plugin/ ~
/usr/local/share/vim/vim60/plugin/ ~
Note that the last one is the value of $VIMRUNTIME which has been expanded.
What if it looks like your plugin is not being loaded? You can find out what
happens when Vim starts up by using the |-V| argument: >
vim -V1
vim -V2
You will see a lot of messages, in between them is a remark about loading the
plugins. It starts with: >
Searching for "plugin/*.vim" in
plugins. It starts with:
Searching for "plugin/**/*.vim" in ~
There you can see where Vim looks for your plugin scripts.
==============================================================================

View File

@@ -1,4 +1,4 @@
*hebrew.txt* For Vim version 7.0. Last change: 2003 May 11
*hebrew.txt* For Vim version 7.1a. Last change: 2003 May 11
VIM REFERENCE MANUAL by Ron Aaron (and Avner Lottem)

View File

@@ -1,4 +1,4 @@
*howto.txt* For Vim version 7.0. Last change: 2006 Apr 02
*howto.txt* For Vim version 7.1a. Last change: 2006 Apr 02
VIM REFERENCE MANUAL by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*intro.txt* For Vim version 7.0. Last change: 2006 Apr 20
*intro.txt* For Vim version 7.1a. Last change: 2006 Apr 20
VIM REFERENCE MANUAL by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*os_amiga.txt* For Vim version 7.0. Last change: 2005 Mar 29
*os_amiga.txt* For Vim version 7.1a. Last change: 2005 Mar 29
VIM REFERENCE MANUAL by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*os_dos.txt* For Vim version 7.0. Last change: 2006 Mar 30
*os_dos.txt* For Vim version 7.1a. Last change: 2006 Mar 30
VIM REFERENCE MANUAL by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*os_win32.txt* For Vim version 7.0. Last change: 2006 Apr 30
*os_win32.txt* For Vim version 7.1a. Last change: 2007 Apr 22
VIM REFERENCE MANUAL by George Reilly
@@ -269,7 +269,7 @@ A. When writing a file Vim renames the original file, this is a backup (in
Q. How do I get to see the output of ":make" while it's running?
A. Basically what you need is to put a tee program that will copy its input
(the output from make) to both stdout and to the errorfile. You can find a
copy of tee (and a number of other GNU tools tools) at
copy of tee (and a number of other GNU tools) at
http://gnuwin32.sourceforge.net or http://unxutils.sourceforge.net
Alternatively, try the more recent Cygnus version of the GNU tools at
http://www.cygwin.com Other Unix-style tools for Win32 are listed at

View File

@@ -1,4 +1,4 @@
*pattern.txt* For Vim version 7.0. Last change: 2006 Apr 30
*pattern.txt* For Vim version 7.1a. Last change: 2007 Apr 24
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -587,7 +587,7 @@ overview.
{Vi does not have any of these}
n and m are positive decimal numbers or zero
*non-greedy*
If a "-" appears immediately after the "{", then a shortest match
first algorithm is used (see example below). In particular, "\{-}" is
the same as "*" but uses the shortest match first algorithm. BUT: A
@@ -969,7 +969,7 @@ x A single character, with no special meaning, matches itself
[xyz] any 'x', 'y' or 'z'
[a-zA-Z]$ any alphabetic character at the end of a line
\c[a-z]$ same
*/[\n]*
With "\_" prepended the collection also includes the end-of-line.
The same can be done by including "\n" in the collection. The
end-of-line is also matched when the collection starts with "^"! Thus
@@ -1042,6 +1042,7 @@ x A single character, with no special meaning, matches itself
\t <Tab>
\r <CR> (NOT end-of-line!)
\b <BS>
\n line break, see above |/[\n]|
\d123 decimal number of character
\o40 octal number of character up to 0377
\x20 hexadecimal number of character up to 0xff
@@ -1068,6 +1069,8 @@ x A single character, with no special meaning, matches itself
You don't often have to use it, but it is possible. Example: >
/\<r\%[[eo]ad]\>
< Matches the words "r", "re", "ro", "rea", "roa", "read" and "road".
There can be no \(\), \%(\) or \z(\) items inside the [] and \%[] does
not nest.
{not available when compiled without the +syntax feature}
*/\%d* */\%x* */\%o* */\%u* */\%U* *E678*
@@ -1145,7 +1148,7 @@ composing character by itself, except that it doesn't matter what comes before
this.
The order of composing characters matters, even though changing the order
doen't change what a character looks like. This may change in the future.
doesn't change what a character looks like. This may change in the future.
==============================================================================
9. Compare with Perl patterns *perl-patterns*
@@ -1219,6 +1222,10 @@ Finally, these constructs are unique to Perl:
'ignorecase' does not apply, use |/\c| in the pattern to
ignore case. Otherwise case is not ignored.
When matching end-of-line and Vim redraws only part of the
display you may get unexpected results. That is because Vim
looks for a match in the line where redrawing starts.
Also see |matcharg()|, it returns the highlight group and
pattern of a previous :match command.

View File

@@ -1,4 +1,4 @@
*pi_spec.txt* For Vim version 7.0. Last change: 2006 Apr 24
*pi_spec.txt* For Vim version 7.1a. Last change: 2006 Apr 24
by Gustavo Niemeyer ~

View File

@@ -1,4 +1,4 @@
*quotes.txt* For Vim version 7.0. Last change: 2006 Apr 24
*quotes.txt* For Vim version 7.1a. Last change: 2006 Apr 24
VIM REFERENCE MANUAL by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*remote.txt* For Vim version 7.0. Last change: 2006 Apr 30
*remote.txt* For Vim version 7.1a. Last change: 2006 Apr 30
VIM REFERENCE MANUAL by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*repeat.txt* For Vim version 7.0. Last change: 2006 Apr 30
*repeat.txt* For Vim version 7.1a. Last change: 2007 Jan 07
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -53,6 +53,13 @@ selection, the same SIZE of area is used, see |visual-repeat|.
:[range]v[global]/{pattern}/[cmd]
Same as :g!.
Instead of the '/' which surrounds the {pattern}, you can use any other
single byte character, but not an alphanumeric character, '\', '"' or '|'.
This is useful if you want to include a '/' in the search pattern or
replacement string.
For the definition of a pattern, see |pattern|.
The global commands work by first scanning through the [range] lines and
marking each line where a match occurs (for a multi-line pattern, only the
start of the match matters).
@@ -656,4 +663,7 @@ mind there are various things that may clobber the results:
- Profiling may give weird results on multi-processor systems, when sleep
mode kicks in or the processor frequency is reduced to save power.
- The "self" time is wrong when a function is used recursively.
vim:tw=78:ts=8:ft=help:norl:

View File

@@ -1,4 +1,4 @@
*scroll.txt* For Vim version 7.0. Last change: 2006 Apr 24
*scroll.txt* For Vim version 7.1a. Last change: 2006 Aug 27
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -223,7 +223,7 @@ jump to a location where the current window's relative offset is valid. This
behavior can be changed by clearing the 'jump' flag from the 'scrollopt'
option.
*syncbind* *:syncbind*
*syncbind* *:syncbind* *:sync*
:syncbind Force all 'scrollbind' windows to have the same
relative offset. I.e., when any of the 'scrollbind'
windows is scrolled to the top of its buffer, all of

View File

@@ -1,4 +1,4 @@
*spell.txt* For Vim version 7.0. Last change: 2006 Apr 30
*spell.txt* For Vim version 7.1a. Last change: 2007 Apr 22
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -16,6 +16,10 @@ Spell checking *spell*
Spell checking is not available when the |+syntax| feature has been disabled
at compile time.
Note: There also is a vimspell plugin. If you have it you can do ":help
vimspell" to find about it. But you will probably want to get rid of the
plugin and use the 'spell' option instead, it works better.
==============================================================================
1. Quick start *spell-quickstart*
@@ -409,6 +413,7 @@ done:
For the second method adding the @NoSpell cluster will disable spell checking
again. This can be used, for example, to add @Spell to the comments of a
program, and add @NoSpell for items that shouldn't be checked.
Also see |:syn-spell| for text that is not in a syntax item.
VIM SCRIPTS
@@ -465,7 +470,7 @@ the word list and keeps it small.
You can create a Vim spell file from the .aff and .dic files that Myspell
uses. Myspell is used by OpenOffice.org and Mozilla. You should be able to
find them here:
http://lingucomponent.openoffice.org/spell_dic.html
http://wiki.services.openoffice.org/wiki/Dictionaries
You can also use a plain word list. The results are the same, the choice
depends on what word lists you can find.
@@ -546,7 +551,7 @@ following procedure is recommended:
2. Make a copy of these files to xx_YY.orig.aff and xx_YY.orig.dic.
3. Change the xx_YY.aff and xx_YY.dic files to remove bad words, add missing
words, define word characters with FOL/LOW/UPP, etc. The distributed
"src/spell/*.diff" files can be used.
"*.diff" files can be used.
4. Start Vim with the right locale and use |:mkspell| to generate the Vim
spell file.
5. Try out the spell file with ":set spell spelllang=xx" if you wrote it in
@@ -646,7 +651,7 @@ exceptions:
only ASCII letters for most of the words.
The default "spellfile.vim" plugin uses this autocommand, if you define your
autocommand afterwars you may want to use ":au! SpellFileMissing" to overrule
autocommand afterwards you may want to use ":au! SpellFileMissing" to overrule
it. If you define your autocommand before the plugin is loaded it will notice
this and not do anything.
@@ -1332,7 +1337,7 @@ With the example "ideeen" has three syllables, counted by "i", "ee" and "e".
Only case-folded letters need to be included.
Above another way to restrict compounding was mentioned above: Adding the
Another way to restrict compounding was mentioned above: Adding the
|spell-COMPOUNDFORBIDFLAG| flag to an affix causes all words that are made
with that affix not be be used for compounding.
@@ -1510,7 +1515,7 @@ COMPLEXPREFIXES (Hunspell) *spell-COMPLEXPREFIXES*
Enables using two prefixes. Not supported.
COMPOUND (Hunspell) *spell-COMPOUND*
This is one line with the count of COMPOUND items, followd by
This is one line with the count of COMPOUND items, followed by
that many COMPOUND lines with a pattern.
Remove the first line with the count and rename the other
items to COMPOUNDRULE |spell-COMPOUNDRULE|

View File

@@ -1,4 +1,4 @@
*sql.txt* For Vim version 7.0. Last change: Wed Apr 26 2006 3:05:33 PM
*sql.txt* For Vim version 7.1a. Last change: Wed Apr 26 2006 3:05:33 PM
by David Fishburn
@@ -632,7 +632,7 @@ your |vimrc|: >
- When completing tables, procedure or views and using dbext.vim 3.00
or higher the list of objects will also include the owner name.
When completing these objects and omni_sql_include_owner is enabled
the owner name will be be replaced. >
the owner name will be replaced. >
omni_sql_precache_syntax_groups
< - Default:

View File

@@ -1,4 +1,4 @@
*starting.txt* For Vim version 7.0. Last change: 2006 Apr 25
*starting.txt* For Vim version 7.1a. Last change: 2007 Apr 22
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -311,12 +311,16 @@ a slash. Thus "-R" means recovery and "-/R" readonly.
Messages will be given for each file that is ":source"d and
for reading or writing a viminfo file. Can be used to find
out what is happening upon startup and exit. {not in Vi}
Example: >
vim -V8 foobar
-V[N]{filename}
Like -V and set 'verbosefile' to {filename}. The result is
that messages are not displayed but written to the file
{filename}. {filename} must not start with a digit.
Example: >
vim -V20vimlog foobar
<
*-D*
-D Debugging. Go to debugging mode when executing the first
command from a script. |debug-mode|
@@ -537,7 +541,7 @@ a slash. Thus "-R" means recovery and "-/R" readonly.
See |--remote-expr|. {not in Vi}
--serverlist Output a list of Vim server names and exit. See
See |--serverlist|. {not in Vi}
|--serverlist|. {not in Vi}
--socketid {id} *--socketid*
GTK+ GUI Vim only. Make gvim try to use GtkPlug mechanism, so
@@ -905,9 +909,10 @@ set, it will be set to 'nocompatible'. This has the side effect of setting or
resetting other options (see 'compatible'). But only the options that have
not been set or reset will be changed. This has the same effect like the
value of 'compatible' had this value when starting Vim. Note that this
doesn't happen for the system-wide vimrc file. It does also happen for gvimrc
files. The $MYVIMRC or $MYGVIMRC file will be set to the first found vimrc
and/or gvimrc file.
doesn't happen for the system-wide vimrc file nor when Vim was started with
the |-u| command line argument. It does also happen for gvimrc files. The
$MYVIMRC or $MYGVIMRC file will be set to the first found vimrc and/or gvimrc
file.
But there is a side effect of setting or resetting 'compatible' at the moment
a .vimrc file is found: Mappings are interpreted the moment they are
@@ -1200,8 +1205,8 @@ resulting file, when executed with a ":source" command:
including hidden and unloaded buffers. Otherwise only buffers in windows
are restored.
8. Restores all windows with the same layout. If 'sessionoptions' contains
contains "help", help windows are restored. If 'sessionoptions' contains
"blank", windows editing a buffer without a name will be restored.
"help", help windows are restored. If 'sessionoptions' contains "blank",
windows editing a buffer without a name will be restored.
If 'sessionoptions' contains "winsize" and no (help/blank) windows were
left out, the window sizes are restored (relative to the screen size).
Otherwise, the windows are just given sensible sizes.

View File

@@ -1,4 +1,4 @@
*syntax.txt* For Vim version 7.0. Last change: 2006 Apr 30
*syntax.txt* For Vim version 7.1a. Last change: 2007 May 03
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -467,52 +467,9 @@ abel_obsolete_ok obsolete keywords are statements, not errors
abel_cpp_comments_illegal do not interpret '//' as inline comment leader
ADA *ada.vim* *ft-ada-syntax*
ADA
This mode is designed for the 1995 edition of Ada ("Ada95"), which
includes support for objected-programming, protected types, and so on.
It handles code written for the original Ada language
("Ada83" or "Ada87") as well, though Ada83 code which uses Ada95-only
keywords will be wrongly colored (such code should be fixed anyway).
For more information about Ada, see http://www.adapower.com.
The Ada mode handles a number of situations cleanly.
For example, it knows that the "-" in "-5" is a number, but the same
character in "A-5" is an operator. Normally, a "with" or "use" clause
referencing another compilation unit is colored the same way as C's
"#include" is colored. If you have "Conditional" or "Repeat"
groups colored differently, then "end if" and "end loop" will be
colored as part of those respective groups.
You can set these to different colors using vim's "highlight" command
(e.g., to change how loops are displayed, enter the command
":hi Repeat" followed by the color specification; on simple terminals
the color specification ctermfg=White often shows well).
There are several options you can select in this Ada mode.
To enable them, assign a value to the option. For example, to turn one on:
let ada_standard_types = 1
To disable them use ":unlet". Example:
unlet ada_standard_types = 1
You can just use ":" and type these into the command line to set these
temporarily before loading an Ada file. You can make these option settings
permanent by adding the "let" command(s), without a colon,
to your "~/.vimrc" file.
Here are the Ada mode options:
Variable Action ~
ada_standard_types Highlight types in package Standard (e.g., "Float")
ada_space_errors Highlight extraneous errors in spaces...
ada_no_trail_space_error but ignore trailing spaces at the end of a line
ada_no_tab_space_error but ignore tabs after spaces
ada_withuse_ordinary Show "with" and "use" as ordinary keywords
(when used to reference other compilation units
they're normally highlighted specially).
ada_begin_preproc Show all begin-like keywords using the coloring
of C preprocessor commands.
Even on a slow (90Mhz) PC this mode works quickly, but if you find
the performance unacceptable, turn on ada_withuse_ordinary.
See |ft-ada-syntax|
ANT *ant.vim* *ft-ant-syntax*
@@ -903,10 +860,6 @@ or in a modeline by appending '.doxygen' to the syntax of the file. Example: >
or >
// vim:syntax=c.doxygen
To use doxygen formatting on top of any filetype, add the following to your
.vimrc for each filetype, replacing {filetype} with the relevent value. >
:let g:syntax_extra_{filetype}='doxygen'
It can also be done automaticly for c, cpp and idl files by setting the global
or buffer-local variable load_doxygen_syntax. This is done by adding the
following to your .vimrc. >
@@ -2339,6 +2292,8 @@ Folding can be enabled by defining "ruby_fold": >
This will set the 'foldmethod' option to "syntax" and allow folding of
classes, modules, methods, code blocks, heredocs and comments.
SCHEME *scheme.vim* *ft-scheme-syntax*
By default only R5RS keywords are highlighted and properly indented.
@@ -2598,6 +2553,16 @@ If you have a slow computer, you may wish to reduce the values for >
increase them. This primarily affects synchronizing (i.e. just what group,
if any, is the text at the top of the screen supposed to be in?).
*tex-morecommands* *tex-package*
Wish To Highlight More Commmands? ~
LaTeX is a programmable language, and so there are thousands of packages full
of specialized LaTeX commands, syntax, and fonts. If you're using such a
package you'll often wish that the distributed syntax/tex.vim would support
it. However, clearly this is impractical. So please consider using the
techniques in |mysyntaxfile-add| to extend or modify the highlighting provided
by syntax/tex.vim.
*tex-error*
Excessive Error Highlighting? ~
@@ -4396,7 +4361,7 @@ Put these lines in your Makefile:
# Make a highlight file for types. Requires Exuberant ctags and awk
types: types.vim
types.vim: *.[ch]
ctags -i=gstuS -o- *.[ch] |\
ctags --c-kinds=gstu -o- *.[ch] |\
awk 'BEGIN{printf("syntax keyword Type\t")}\
{printf("%s ", $$1)}END{print ""}' > $@
@@ -4504,7 +4469,7 @@ You probably want to use these X resources (in your ~/.Xdefaults file):
[Note: The cursorColor is required to work around a bug, which changes the
cursor color to the color of the last drawn text. This has been fixed by a
newer version of xterm, but not everybody is it using yet.]
newer version of xterm, but not everybody is using it yet.]
To get these right away, reload the .Xdefaults file to the X Option database
Manager (you only need to do this when you just changed the .Xdefaults file): >
@@ -4520,7 +4485,7 @@ these resources:
XTerm*cursorColor: White
*hpterm-color*
These settings work (more or less) for a hpterm, which only supports 8
These settings work (more or less) for an hpterm, which only supports 8
foreground colors: >
:if has("terminfo")
: set t_Co=8

View File

@@ -1,4 +1,4 @@
*tagsrch.txt* For Vim version 7.0. Last change: 2006 Apr 24
*tagsrch.txt* For Vim version 7.1a. Last change: 2006 Apr 24
VIM REFERENCE MANUAL by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*todo.txt* For Vim version 7.0. Last change: 2006 May 07
*todo.txt* For Vim version 7.1a. Last change: 2007 May 05
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -30,9 +30,476 @@ be worked on, but only if you sponsor Vim development. See |sponsor|.
*known-bugs*
-------------------- Known bugs and current work -----------------------
Patch to make virtcol([123, '$']) do the right thing. (Michael Schaap)
Insert mode completion: CTRL-N and CTRL-P work differently and they both don't
work as expected. (Bernhard Walle, 2007 Feb 27)
glob() doesn't work correctly with single quotes and 'shell' set to /bin/sh.
(Adri Verhoef, Charles Campbell 2007 Mar 26)
Splitting quickfix window messes up window layout. (Marius Gedminas, 2007 Apr
25)
Replace ccomplete.vim by cppcomplete.vim from www.vim.org? script 1520
(Martin Stubenschrott)
ctags -R --c++-kinds=+p --fields=+iaS --extra=+q .
Making the German sharp s uppercase doesn't work properly: one character less
is uppercased in "gUe".
Also: latin2 has the same character but it isn't uppercased there.
Mac: After a ":vsplit" the left scrollbar doesn't appear until 'columns' is
changed or the window is resized.
Mac: Patch for Mac GUI tabline. (Nicolas Weber, 2006 Jul 18, Update 2007 Feb)
New update v6 ~/tmp/guitab.v6.diff (Kyle Wheeler)
When 'virtualedit' is set a "p" of a block just past the end of the line
inserts before the cursor. (Engelke)
Using Aap to build Vim: add remarks about how to set personal preferences.
Example on http://www.calmar.ws/tmp/aap.html
GTK: 'bsdir' doesn't work. Sometimes get a "gtk critical error".
Moved some code to append file name to further down in gui_gtk.c
gui_mch_browse(), but "last" value of 'bsdir' still doesn't work.
C syntax: "#define x {" The macro should terminate at the end of the line,
not continue in the next line. (Kelvin Lee, 2006 May 24)
C syntax: {} inside () causes following {} to be highlighted as error.
(Michalis Giannakidis, 2006 Jun 1)
Gnome improvements: Edward Catmur, 2007 Jan 7
Also use Save/Discard for other GUIs
New PHP syntax file, use it? (Peter Hodge)
'foldcolumn' in modeline applied to wrong window when using a session. (Teemu
Likonen, March 19)
Syntax highlighting wrong for transparent region. (Doug Kearns, 2007 Feb 26)
More AmigaOS4 patches. (Peter Bengtsson, Nov 9)
Add v:searchforward variable. Patch by Yakov Lerner, 2006 Nov 18.
Redraw problem in loop. (Yakov Lerner, 2006 Sep 7)
Add option settings to help ftplugin. (David Eggum, 2006 Dec 18)
Use new dutch wordlist for spelling? http://www.opentaal.org/
See remarks from Adri, 2007 Feb 9.
When opening quickfix window, disable spell checking?
Win32: When 'encoding' is "latin1" 'ignorecase' doesn't work for characters
with umlaut. (Joachim Hofmann) toupper_tab[] and tolower_tab[] are not filled
properly?
Completion: Scanning for tags doesn't check for typed key now and then?
Hangs for about 5 seconds. Appears to be caused by finding include files with
"foo/**" in 'path'. (Kalisiak, 2006 July 15)
Completion: When 'completeopt' has "longest" and there is one match the
message is "back at original" and typing a char doesn't leave completion mode.
(Igor Prischepoff, 2006 Oct 5)
Completion: When using CTRL-X O and there is only "struct." before the cursor,
typing one char to reduce the matches, then BS completion stops. Should keep
completion if still no less than what we started with.
Completion: don't stop completion when typing a space when completing full
lines? Also when completing file names? Only stop completion when there are
no matches?
After using BS completion only stops when typing a space. Many people want to
stop at non-word characters, e.g., '('. Add an option for this? Or check
vim_iswordc() before calling ins_compl_addleader()?
searchpos() doesn't use match under cursor at start of line. (Viktor
Kojouharov, 2006 Nov 16)
When FEAT_BYTEOFF is defined but FEAT_NETBEANS_INTG is not compiling fails.
Add FEAT_BYTEOFF to the check at line 1180 in feature.h
Color for cUserLabel should differ from case label, so that a mistake in a
switch list is noticed:
switch (i)
{
case 1:
foobar:
}
":s" command removes combining characters. (Ron Aaron, 2006 May 17, 2006 Dec 7)
Look at http://www.gtk-server.org/ . It has a Vim script implementation.
Changes for Win32 makefile. (Mike Williams, 2007 Jan 22, Alexei Alexandrov,
2007 Feb 8)
Patch for Win32 clipboard under Cygwin. (Frodak Baksik, Feb 15)
Sutcliffe says it works well.
Win32: Patch for convert_filterW(). (Taro Muraoka, 2007 Mar 2)
Win32: XPM support only works with path without spaces. Patch by Mathias
Michaelis, 2006 Jun 9. Another patch for more path names, 2006 May 31.
New version: http://members.tcnet.ch/michaelis/vim/patches.zip (also for other
patches by Mathias, see mail Feb 22)
Win32: compiling with normal features and OLE fails. Patch by Mathias
Michaelis, 2006 Jun 4.
Win32: echo doesn't work for gvim.exe.mnf. Use inline file. Patch by Mathias
Michaelis. http://groups.yahoo.com/group/vimdev/message/43765
Patch that includes this and does more by George Reilly, 2007 Feb 12
Win16: include patches to make Win16 version work. (Vince Negri, 2006 May 22)
Win32: after "[I" showing matches, scroll wheel messes up screen. (Tsakiridis,
2007 Feb 18)
Win32: using CTRL-S in Insert mode doesn't remove the "+" from the tab pages
label. (Tsakiridis, 2007 Feb 18)
Win32: remote editing doesn't work when the current directory name contains
"[]". (Ivan Tishchenko, 2007 March 1)
Win64: diff.exe crashes on Win64. (Julianne Bailey, 2006 Dec 12)
Build another diff.exe somehow?
Win64: Seek error in swap file for a very big file (3 Gbyte). Check storing
pointer in long and seek offset in 64 bit var.
When doing "gvim --remote-tab foo" while gvim is minimized the tab pages line
only shows the current label, not the others.
Problem finding swap file for recovery. (Gautam Iyer, 2006 May 16)
When setting 'keymap' twice the b:keymap_name variable isn't set. (Milan
Berta, 2007 Mar 9) Has something to do with 'iminsert'.
Problem with CursorHoldI? (Max Dyckhoff, 2006 Nov 10)
UTF-8: mapping a multi-byte key where the second byte is 0x80 doesn't appear
to work. (Tony Mechelynck, 2007 March 2)
The str2special() function doesn't handle multi-byte characters properly.
Patch from Vladimir Vichniakov, 2007 Apr 24.
find_special_key() also has this problem.
In debug mode, using CTRL-R = to evaluate a function causes stepping through
the function. (Hari Krishna Dara, 2006 Jun 28)
":let &shiftwidth = 'asdf'" doesn't produce an error message.
C++ indenting wrong with "=". (James Kanze, 2007 Jan 26)
"zug" reports wrong file. problem with Namebuff? (Lawrence Kesteloot, 2006 Sep
10)
":lockvar" should use copyID to avoid endless loop.
Gvim: dialog for closing Vim should check if Vim is busy writing a file. Then
use a different dialog: "busy saving, really quit? yes / no".
Win32: editing remote file d:\a[1]\aa.txt doesn't work. (Liu Yubao, 2006 May
29)
"zw" doesn't appear to work. (Luis A Florit, 2006 Jun 23, 24)
"dw" in a line with one character deletes the line. Vi and nvi don't do this.
Is it intentional or not? (Kjell Arne Rekaa)
Check other interfaces for changing curbuf in a wrong way. Patch like for
if_ruby.c.
Spell checking in popup menu: If the only problem is the case of the first
character, don't offer "ignore" and "add to word list".
":helpgrep" should use the directory from 'helpfile'.
The need_fileinfo flag is messy. Instead make the message right away and put
it in keep_msg?
More-prompt is skipped when doing this; (Randall W. Morris, Jun 17)
:au
<Space>
b
<Space>
Editing a file remotely that matches 'wildignore' results in a "no match"
error. Should only happen when there are wildards, not when giving the file
name literally, and esp. if there is only one name.
When 'expandtab' is set then a Tab copied for 'copyindent' is expanded to
spaces, even when 'preserveindent' is set. (Alexei Alexandrov, Mar 7)
Test 61 fails sometimes. This is a timing problem: "sleep 2" sometimes takes
longer than 2 seconds.
VMS: while editing a file found in complex, Vim will save file into the first
directory of the path and not to the original location of the file.
(Zoltan Arpadffy)
input() completion should not insert a backslash to escape a space in a file
name?
getpos()/setpos() don't include curswant. getpos() could return a fifth
element. setpos() could accept an optional fifth element.
Ruby completion is insecure. Can this be fixed?
":confirm w" does give a prompt when 'readonly' is set, but not when the file
permissions are read-only. Both can be overruled by ":w!" thus it would be
logical to get a prompt for both. (Michael Schaap)
When 'backupskip' is set from $TEMP special characters need to be escaped.
(patch by Grembowietz, 2007 Feb 26, not quite right)
Another problem is that file_pat_to_reg_pat() doesn't recognize "\\", so "\\("
will be seen as a path separator plus "\(".
":python os.chdir('/tmp')" makes short buffer names invalid. (Xavier de Gaye)
Check directory and call shorten_fnames()?
aucmd_prepbuf() should also use a window in another tab page.
Substituting an area with a line break with almost the same area does change
the Visual area. Can this be fixed? (James Vega, 2006 Sept 15)
Windows installer could add a "open in new tab of existing Vim" menu entry.
:s/e/E/l not only lists but also shows line number. Is that right?
(Yakov Lerner, 2006 Jul 27)
GUI: When combining fg en bg make sure they are not equal.
Use different pt_br dictionary for spell checking. (Jackson A. Aquino, 2006
Jun 5)
Mac: Using gvim: netrw window disappears. (Nick Lo, 2006 Jun 21)
When 'bomb' is set or reset the file should be considered modified. (Tony
Mechelynck) Handle like 'endofline'.
Add an option to specify the character to use when a double-width character is
moved to the next line. Default '>', set to a space to blank it out. Check
that char is single width when it's set (compare with 'listchars').
Update main.aap for installing on the Mac.
The generated vim.bat can avoid the loop for NT. (Carl Zmola, 2006 Sep 3)
Session file creation: 'autochdir' causes trouble. Keep it off until after
loading all files.
C completion: doesn't work after aa[0]->, where aa is an array of structures.
(W. de Hoog, 2006 Aug 12)
The spellfile plugin checks for a writable "spell" directory. A user may have
a writable runtime directory without a "spell" directory, it could be created
then.
These two abbreviations don't give the same result:
let asdfasdf = "xyz\<Left>"
cabbr XXX <C-R>=asdfasdf<CR>
cabbr YYY xyz<Left>
Michael Dietrich: maximized gvim sometimes displays output of external command
partly. (2006 Dec 7)
In FileChangedShell command it's no longer allowed to switch to another
buffer. But the changed buffer may differ from the current buffer, how to
reload it then?
New syntax files for fstab and resolv from Radu Dineiu, David Necas did
previous version.
For Aap: include a config.arg.example file with hints how to use config.arg.
Linux distributions:
- Suggest compiling xterm with --enable-tcap-query, so that nr of colors is
known to Vim. 88 colors instead of 16 works better. See ":help
xfree-xterm".
- Suggest including bare "vi" and "vim" with X11, syntax, etc.
Completion menu: For a wrapping line, completing a long file name, only the
start of the path is shown in the menu. Should move the menu to the right to
show more text of the completions. Shorten the items that don't fit in the
middle?
When running inside screen it's possible to kill the X server and restart it
(using pty's the program can keep on running). Vim dies because it looses the
connection to the X server. Can Vim simply quit using the X server instead of
dying? Also relevant when running in a console.
Accessing file#var in a function should not need the g: prepended.
When ":cn" moves to an error in the same line the message isn't shortened.
Only skip shortening for ":cc"?
Win32: The matchparen plugin doesn't update the match when scrolling with the
mouse wheel. (Ilya Bobir, 2006 Jun 27)
Write "making vim work better" for the docs (mostly pointers): *nice*
- sourcing $VIMRUNTIME/vimrc_example.vim
- setting 'mouse' to "a"
- getting colors in xterm
- compiling Vim with X11, GUI, etc.
Problem with ":call" and dictionary function. Hari Krishna Dara, Charles
Campbell 2006 Jul 06.
Syntax HL error caused by "containedin". (Peter Hodge, 2006 Oct 6)
GTK: When maximizing Vim the result is slightly smaller, the filler border is
not there, and the "maximize" button is still there. Clicking it again does
give a maximized window. (Darren Hiebert)
Problem is that gui_mch_set_text_area_pos() is invoked to change the text area
size, which causes the toplevel window to resize. When doing this while the
size is already right the filler remains there.
Detect using the maximize button (GdkWindowState bit
GDK_WINDOW_STATE_MAXIMIZED) and set it again?
Another resizing problem when setting 'columns' and 'lines' to a very large
number. (Tony Mechelynck, 2007 Feb 6)
Mutt files are not always recognized. Change pattern to include
non-alphanumeric characters. (Gary Johnson, 2006 Jul 25)
Problem with using :redir in user command completion function? (Hari Krishna
Dara, 2006 June 21)
After starting Vim, using '0 to jump somewhere in a file, ":sp" doesn't center
the cursor line. It works OK after some other commands.
Screen redrawing when continuously updating the buffer and resizing the
terminal. (Yakov Lerner, 2006 Sept 7)
Win32: Is it possible to have both postscript and Win32 printing?
Does multi-byte printing with ":hardcopy" work? Add remark in documentation
about this.
'thesaurus' doesn't work when 'infercase' is set. (Mohsin, 2006 May 30)
There should be something about spell checking in the user manual.
Check: Running Vim in a console and still having connect to the X server for
copy/paste: is stopping the X server handled gracefully? Should catch the X
error and stop using the connection to the server.
Problem with 'cdpath' on MS-Windows when a directory is equal to $HOME. (2006
Jul 26, Gary Johnson)
In the Netbeans interface add a "vimeval" function, so that the other side can
check the result of has("patch13").
":py" asks for an argument, ":py asd" then gives the error that ":py" isn't
implemented. Should already happen for ":py".
Add command modifier that skips wildcard expansion, so that you don't need to
put backslashes before special chars, only for white space.
Win32 GUI: confirm() with zero default should not have a choice selected.
Win32: When the GUI tab pages line is displayed Vim jumps from the secondary
to the primary monitor. (Afton Lewis, 2007 Mar 9) Old resizing problem?
GTK GUI: When the completion popup menu is used scrolling another window by
the scrollbar is OK, but using the scroll wheel it behaves line <Enter>.
"cit" used on <foo></foo> deletes <foo>. Should not delete anything and start
insertion, like "ci'" does on "". (Michal Bozon)
Allow more than 3 ":match" items.
The magic clipboard format "VimClipboard2" appears in several places. Should
be only one.
It's difficult to debug numbered functions (function in a Dictionary). Print
the function name before resolving it to a number?
let d = {}
fun! d.foo()
echo "here"
endfun
call d.foo(9)
Add a mark for the other end of the Visual area (VIsual pos). '< and '> are
only set after Visual moded is ended.
Small problem displaying diff filler line when opening windows with a script.
(David Luyer, 2007 Mar 1 ~/Mail/oldmail/mool/in.15872 )
When pattern for ":sort" is empty, use last search pattern. Allows trying out
the pattern first. (Brian McKee)
Is it allowed that 'backupext' is empty? Problems when backup is in same dir
as original file? If it's OK don't compare with 'patchmode'. (Thierry Closen)
Patch for supporting count before CR in quickfix window. (AOYAMA Shotaro, 2007
Jan 1)
Patch for adding ":lscscope". (Navdeep Parhar, 2007 Apr 26; update Apr 28)
Patch for improving regexp speed by not freeing memory. (Alexei Alexandrov,
2007 Feb 6)
xterm should be able to pass focus changes to Vim, so that Vim can check for
buffers that changed. Perhaps in misc.c, function selectwindow().
Xterm 224 supports it!
Omni completion takes the wrong structure for variable arguments. (Bill
McCarthy, 2007 Feb 18)
When completing from another file that uses a different encoding completion
text has the wrong encoding. E.g., when 'encoding' is utf-8 and file is
latin1. Example from Gombault Damien, 2007 Mar 24.
Completing ":echohl" argument should include "None". (Ori Avtalion)
Vim 7.2:
- Search offset doesn't work for multibyte character. Patch from Yukihiro
Nakadaira, 2006 Jul 18.
Changes the offset from counting bytes to counting characters.
- Rename the tutor files from tutor.gr.* to tutor.el.*. Greece vs Greek.
Make all tutor files available in utf-8.
- Remove ! for ":cgetfile" and ":lgetfile". (patch from Yegappan Lakshmanan,
2007 Mar 9)
- Add blowfish encryption. Openssl has an implementation. Also by Paul
Kocher (LGPL), close to original. Mohsin also has some ideas.
Take four bytes and turn them into unsigned to avoid byte-order problems.
Need to buffer up to 7 bytes to align on 8 byte boundaries.
- Rename doc/sql.vim doc/ft_sql.vim.
- Change "command-line" to "[Command Line]" for the command line buffer
name in ex_window().
- Move including fcntl.h to vim.h, before O_NOFOLLOW, and remove it from all
.c files.
- ":{range}source": source the lines from the file.
You can already yank lines and use :@" to execute them.
Most of do_source() would not be used, need a new function.
It's easy when not doing breakpoints or profiling.
Patches:
- Add 'cscopeignorecase' option. (Liang Wenzhi, 2006 Sept 3)
- Argument for feedkeys() to prepend to typeahead (Yakov Lerner, 2006 Oct
21)
- Load intl.dll too, not only libintl.dll. (Mike Williams, 2006 May 9, docs
patch May 10)
- Extra argument to strtrans() to translate special keys to their name (Eric
Arnold, 2006 May 22)
- 'threglookexp' option: only match with first word in thesaurus file.
(Jakson A. Aquino, 2006 Jun 14)
- Mac: indicate whether a buffer was modified. (Nicolas Weber, 2006 Jun 30)
- Allow negative 'nrwidth' for left aligning. (Nathan Laredo, 2006 Aug 16)
- ml_append_string(): efficiently append to an existing line. (Brad
Beveridge, 2006 Aug 26) Use in some situations, e.g., when pasting a
character at a time?
- gettabvar() and settabvar() functions. (Yegappan Lakshmanan, 2006 Sep 8)
- recognize hex numbers better. (Mark Manning, 2006 Sep 13)
Awaiting updated patches:
9 Mac unicode patch (Da Woon Jung, Eckehard Berns):
@@ -44,6 +511,8 @@ Awaiting updated patches:
- With 'nopaste' pasting is wrong, with 'paste' Command-V doesn't work.
(Alan Schmitt)
- remove 'macatsui' option when this has been fixed.
- when 'macatsui' is off should we always convert to "macroman" and ignore
'termencoding'?
9 HTML indenting can be slow. Caused by using searchpair(). Can search()
be used instead?
8 Win32: Add minidump generation. (George Reilly, 2006 Apr 24)
@@ -89,6 +558,8 @@ Awaiting updated patches:
(2003 May 13)
raisewin() raise gvim window (see HierAssist patch for
Tcl implementation ~/vim/HierAssist/ )
taglist() add argument to specify maximum number of matches.
useful for interactive things or completion.
7 Make globpath() also work with upwards search. (Brian Medley)
7 Add patch from Benoit Cerrina to integrate Vim and Perl functions
better. Now also works for Ruby (2001 Nov 10)
@@ -211,6 +682,8 @@ GTK+ GUI known bugs:
Win32 GUI known bugs:
- Win32: tearoff menu window should have a scrollbar when it's taller than
the screen.
8 non-ASCII font names don't work. Need to convert from 'encoding' and use
the wide functions.
8 On Windows 98 the unicows library is needed to support functions with UCS2
file names. Can we load unicows.dll dynamically?
8 When the primary monitor is below or right of the secondary monitor and
@@ -252,7 +725,6 @@ Win32 GUI known bugs:
mouse position. Catch WM_MOUSEACTIVATE. (Luevelsmeyer)
8 Win32: When mouse is hidden and in the toolbar, moving it won't make it
appear. (Sami Salonen)
8 Windows NT: writing to aux.* makes Vim hang. (Acevedo)
8 Win32 GUI: With maximized window, ":set go-=r" doesn't use the space that
comes available. (Poucet) It works OK on Win 98 but doesn't work on Win
NT 4.0. Leaves a grey area where the scrollbar was. ":set go+=r" also
@@ -569,12 +1041,16 @@ Macintosh:
8 Inputting Unicode characters does not work in the terminal. They appear
to arrive as upper and lower bytes. (David Brown, 2004 April 17)
8 Typing Unicode characters doesn't work at all in the GUI.
8 inputdialog() doesn't resize when giving more text lines. (David Fishburn,
2006 Sept 28)
9 Problems in Carbon version for OS X: (Benji Fisher)
- keyboard shortcuts in the menus get lost.
8 The Vim/About menu doesn't work.
8 ":gui" doesn't fork. Enabling the code in gui.c to fork causes a SEGV.
8 Define vim_mkdir() for Macintosh.
8 Define mch_writable() for Macintosh.
8 Some file systems are case-sensitive, some are not. Turn
CASE_INSENSITIVE_FILENAME into an option, at least for completion.
9 When DiskLock is running, using a swap file causes a crash. Appears to be
a problem with writing a file that starts with a dot. (Giacalone)
9 On G3 Mac, OS version 8, control strip causes characters messed up when
@@ -587,6 +1063,10 @@ Macintosh:
"Small" problems:
- When using e_secure in do_one_cmd() mention the command being executed,
otherwise it's not clear where it comes from.
8 When disabling FEAT_CMDL_COMPL compilation fails. Would need to avoid
using parse_compl_arg() in eval.c and uc_scan_attr().
9 For Turkish vim_tolower() and vim_toupper() also need to use utf_
functions for characters below 0x80. (Sertacyildiz)
9 When the last edited file is a help file, using '0 in a new Vim doesn't
@@ -606,11 +1086,10 @@ Macintosh:
8 When redirecting and using ":silent" the current column for displaying and
redirection can be different. Use a separate variable to hold the column
for redirection.
7 There is no way to change directory and go back without changing the local
and/or global directory. Add a way to find out if the current window uses
a local directory. Add cdcmd() that returns ":cd" or ":lcd"?
7 The messages for "vim --help" and "vim --version" don't use
'termencoding'.
- Could the hit-enter prompt be avoided when a message only overlaps the
'showcmd' area? Clear that area when the next cmd is typed.
8 When 'scrollbind' is set, a window won't scroll horizontally if the cursor
line is too short. Add a word in 'scrollopt' to allow moving the cursor
to longer line that is visible. A similar thing is done for the GUI when
@@ -629,6 +1108,7 @@ Macintosh:
8 When doing Insert mode completion a mapping cannot recursively call
edit(), because the completion information is global. Put everything in
an allocated structure?
6 Python: ":py raw_input('prompt')" doesn't work. (Manu Hack)
8 Command line completion: buffers "foo.txt" and "../b/foo.txt", completing
":buf foo<Tab>" doesn't find the second one. (George V. Reilly)
7 Output for ":scriptnames" and ":breaklist" should shorten the file names:
@@ -650,9 +1130,6 @@ Macintosh:
7 "[p" doesn't work in Visual mode. (David Brown)
7 The Cygwin and MingW makefiles define "PC", but it's not used anywhere.
Remove? (Dan Sharp)
9 The argument <f-args> of a user command doesn't handle backslashes
properly. "Cmd \ e" is one argument, "Cmd \\ e" still is one argument.
"Cmd \ e" is two arguments, first one ending in space. (Kontra Gergely)
9 User commands use the context of the script they were defined in. This
causes a "s:var" argument to unexpectedly use a variable in the defining
script, not the calling script. Add an argument to ":command":
@@ -684,6 +1161,8 @@ Macintosh:
flag to to the command. Same for ":snomagic". (Johan Spetz)
8 Using ":s" in a function changes the previous replacement string. Save
"old_sub" in save_search_patterns()?
8 Should allow multi-byte characters for the delimiter: ":s+a+b+" where "+"
is a multi-byte character.
8 When appending to a file and 'patchmode' isn't empty, a backup file is
always written, even when the original file already exists.
7 When using "daw" on the last word in a file and this is a single letter,
@@ -699,6 +1178,8 @@ Macintosh:
'foldlevel' is set from 'foldlevelstart'.
8 Also store the line number with the script ID and use it for ":verbose",
so that "set nocompatible" is found when it changes other option values.
When an option is set indirectly mention the command? E.g. when
":diffsplit" sets 'foldmethod'.
8 In the fileformat dialog, "Cancel" isn't translated. Add a global
variable for this. (Eduardo Fernandez)
9 When editing a file with 'readonly' set, there is no check for an existing
@@ -831,6 +1312,8 @@ Macintosh:
8 Dragging the status line doesn't scroll but redraw.
9 Evaluating 'statusline' in build_stl_str_hl() does not properly check for
reaching the end of the available buffer.
Patch to dynamically allocate the buffer for % items. (Eric Arnold, 2006
May 14)
8 When performing incremental search, should abort searching as soon as a
character is typed.
8 When the value of $MAKE contains a path, configure can't handle this.
@@ -890,6 +1373,7 @@ Problems that will (probably) not be solved:
XtOpenDisplay() prints this directly, there is no way to avoid it.
- X windows: Setting 'guifontset' to an illegal value sometimes crashes Vim.
This is caused by a fault in a X library function, can't be solved in Vim.
- Win32 tcl: has("tcl") hangs when the tcl84.dll is from cygwin.
- Motif: When adding a menu item "Find this &Symbol", the "s" in "this" will
be underlined, instead of in "Symbol". Motif doesn't let us specify which
character gets the highlighting.
@@ -987,6 +1471,7 @@ Didn't make it into Vim 7.0:
198 standard http://www.jcp.org/en/jsr/detail?id=198.
Eclim does it: http://eclim.sourceforge.net/ (Eric Van Dewoestine)
Plugin that uses a terminal emulator: http://vimplugin.sf.net
And another one: http://www.satokar.com/viplugin/index.php
- STICKY CURSOR: Add a way of scrolling that leaves the cursor where it is.
Especially when using the scrollbar. Typing a cursor-movement command
scrolls back to where the cursor is.
@@ -1003,6 +1488,8 @@ Didn't make it into Vim 7.0:
Documentation:
8 List of Vim runtime directories. dotvim.txt from Charles Campbell, 2007
Feb 20.
8 The GUI help should explain the Find and Find/Replace dialogs. Add a link
to it from ":promptrepl" and ":promptfind".
8 List of options should mention whether environment variables are expanded
@@ -1084,6 +1571,10 @@ User Friendlier:
Tab pages:
9 GUI implementation for the tab pages line for other systems.
7 GUI: Control over the appearance of the text in the labels (bold, color,
font, etc.)
9 Make it possible to drag a tab page label to another position with the
mouse.
8 Make GUI menu in tab pages line configurable. Like the popup menu.
8 balloons for the tab page labels that are shortened to show the full path.
8 :tabmove +N move tab page N pages forward
@@ -1095,15 +1586,27 @@ Tab pages:
8 Add local options for each tab page? E.g., 'diffopt' could differ between
tab pages.
7 Add local highlighting for each tab page?
7 Add local directory for tab pages? How would this interfere with
window-local directories?
Spell checking:
- Support more regions? Caolan McNamara argues it's needed for es_XX.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=219777
- Unicode defines another quote character: 0x2019. Use it as an equivalent
of a single quote, thus use it as a word character like a quote and match
with words, replacing the curly quote with a single quote.
- Could filter &eacute; things for HTML before doing spell checking.
Similarly for TeX.
- The Hungarian spell file uses four extra characters in the FOL/UPP/LOW
items than other spell files with the ISO-8859-2 encoding, that causes
problem when changing 'spelllang'. There is no obvious way to fix this.
- Considering Hunspell 1.1.4:
What does MAXNGRAMSUGS do?
Is COMPLEXPREFIXES necessary when we have flags for affixes?
- There is no Finnish spell checking file. For openoffic Voikko is now
used, which is based on Malaga: http://home.arcor.de/bjoern-beutel/malaga/
(Teemu Likonen)
8 ":mkspell" still takes much too long in Hungarian dictionary from
hunspell. Only solution appears to be to postpone secondary suffixes.
8 Handle postponed prefix with COMPOUNDPERMITFLAG or COMPOUNDFORBIDFLAG.
@@ -1190,7 +1693,11 @@ Diff mode:
Folding:
(commands still available: zI zJ zK zp zP zq zQ zV zy zY;
secondary: zB zS zT zZ, z=)
8 Vertical folds: looks like vertically split windows, but the cursor moves
through the vertical separator, separator moves when scrolling.
8 Add "z/" and "z?" for searching in not folded text only.
9 Add search pattern item to only match in closed or open fold and/or fold
with certain level. Allows doing ":g/pat/cmd" to work on closed folds.
8 Add different highlighting for a fold line depending on the fold level.
(Noel Henson)
7 Use "++--", "+++--" for different levels instead of "+---" "+----".
@@ -1292,6 +1799,7 @@ Multi-byte characters:
7 In "-- INSERT (lang) --" show the name of the keymap used instead of
"lang". (Ilya Dogolazky)
- Make 'langmap' accept multi-byte characters.
Patch from Konstantin Korikov, 2006 Oct 15.
- Make 'breakat' accept multi-byte characters. Problem: can't use a lookup
table anymore (breakat_flags[]).
Simplistic solution: when 'formatoptions' contains "m" also break a line
@@ -1317,8 +1825,8 @@ Printing:
- Win32: when 'printfont' is empty use 'guifont'.
- Unix: Use some dialog box to do the obvious settings (paper size, printer
name, portrait/landscape, etc).
- PostScript: only works for 7-bit ASCII and EBCDIC. Should support
different 'encoding' values somehow.
- PostScript: Only works for text that can be converted to an 8-bit
character set. How to support Unicode fully?
- Allow specifying the paper size, instead of using a standard size. Same
units as for the margins.
- Support right-to-left text?
@@ -1338,6 +1846,9 @@ Syntax highlighting:
8 When editing a new file without a name and giving it a name (by writing
it) and 'filetype' is not set, detect the filetype. Avoid doing it for
":wq file".
7 For "nextgroup" we have skipwhite, skipnl and skipempty. It would be
really nice to be able to skip with a pattern. Or skip with a syntax
group. (Nikolai Weibull, 2007 Feb 27)
8 Make conversion to HTML faster (Write it in C or pre-compile the script).
9 There is still a redraw bug somewhere. Probably because a cached state is
used in a wrong way. I can't reproduce it...
@@ -1415,6 +1926,9 @@ Syntax highlighting:
8 When using a regexp for "contains=", should delay matching with it until
redrawing happens. Set a flag when a group is added, check this flag when
highlighting starts.
8 Some terminals can display colors like the GUI. Add some setting to use
GUI colors for the terminal? With something to define the escape
sequence.
7 It's possible for an item to be transparent, so that the colors of an item
lower on the stack is used. Also do this with highlighting, so that the
user can set transparent highlighting? E.g. a number in a C comment would
@@ -1483,24 +1997,14 @@ Syntax highlighting:
Built-in script language:
9 Autoload: Add a Vim script in $VIMRUNTIME/tools that takes a file with a
list of script names and a help file and produces a script that can be
sourced to install the scripts in the user's directories.
Use findfile(), so that only file names need to be given:
script plugin/myscript.vim
script autoload/mylib.vim
script autoload/yourlib.vim
helpfile doc/myscript.txt
For the "helpfile" item ":helptags" is run.
7 Execute a function with standard option values. No need to save and
restore option values. Especially useful for new options. Problem: how
to avoid a performance penalty (esp. for string options)?
8 Add referring to key options with "&t_xx". Both for "echo &t_xx" and
":let &t_xx =". Useful for making portable mappings.
- Add "{range}source": execute lines from a buffer.
Alternative: Allow range for ":exec", pass it on to the executed command.
(Webb)
You can already yank lines and use :@" to execute them.
- Add ":let var ?= value", conditional assignment. Patch by Dave Eggum,
2006 Dec 11.
- range for ":exec", pass it on to the executed command. (Webb)
7 ":include" command: just like ":source" but doesn't start a new scriptID?
Will be tricky for the list of script names.
8 Have a look at VSEL. Would it be useful to include? (Bigham)
@@ -1523,7 +2027,16 @@ Built-in script language:
file belongs to a sourced script?
7 Add argument to winwidth() to subtract the space taken by 'foldcolumn',
signs and/or 'number'.
6 Add ++ and -- operators? They only work on variables (lvals), how to
implement this?
8 Add functions:
has(":command") Check if ":command" works. compare function
with "ex_ni". E.g. for ":simalt".
system() With a List argument. Bypasses the shell, use
exec() directly. (Bob Hiestand)
escape() Add argument to specify what to escape with.
modestack() Instead of just the current mode return the
stack of Insert / CTRL-O / :normal things.
realname() Get user name (first, last, full)
user_fullname() patch by Nikolai Weibull, Nov
3 2002
@@ -1561,7 +2074,8 @@ Built-in script language:
column and line number? col("'0") currently returns zero.
8 argc() returns 0 when using "vim -t tag". How to detect that no file was
specified in any way? To be able to jump to the last edited file.
8 Pass the executable name to the Vim scripts in some way. As v:argv0?
8 Pass the command line arguments to Vim scripts in some way. As v:args
List? Or extra parameter to argv()?
8 Add command arguments with three dashes, passed on to Vim scripts.
7 Add optional arguments to user functions:
:func myFunc(arg1, arg2, arg3 = "blah", arg4 = 17)
@@ -1571,6 +2085,7 @@ Built-in script language:
8 The "= register should be writable, if followed by the name of a variable,
option or environment variable.
8 ":let &option" should list the value of the option.
8 ":let Func().foo = value" should work, also when "foo" doesn't exist.
7 Add synIDlist(), making the whole list of syntax items on the syntax stack
available as a List.
8 Add autocommand-event for when a variable is changed:
@@ -1606,6 +2121,9 @@ Robustness:
Performance:
7 For strings up to 3 bytes don't allocate memory, use v_list itself as a
character array. Use VAR_SSTRING (short string).
8 Instead of loading rgb.txt every time a color wasn't recognized load it
once and keep it in memory. Move the code to a common place to avoid
repeating it in various system files.
8 Turn b_syn_ic and b_syn_containedin into b_syn_flags.
9 Loading menu.vim still takes quite a bit of time. How to make it faster?
8 in_id_list() takes much time for syntax highlighting. Cache the result?
@@ -1719,6 +2237,8 @@ Messages:
- Delete message after new command has been entered and have waited for key.
Perhaps after ten seconds?
- Make message history available in "msg" variables: msg1, msg2, .. msg9.
8 When reading from stdin allow suppressing the "reading from stdin"
message.
9 Check handling of overwriting of messages and delays:
Very wrong: errors while redrawing cause endless loop.
When switching to another file and screen scrolls because of the long
@@ -1840,6 +2360,9 @@ Tags:
before the previous ":tag" command. (Webb)
- When doing "[^I" or "[^D" add position to tag stack.
- Add command to put current position to tag stack: ":tpush".
- Add functions to save and restore the tag stack? Or a command to switch
to another tag stack? So that you can do something else and come back to
what you were working on.
7 When using CTRL-] on someClass::someMethod, separate class from method and
use ":ta class:someClass someMethod".
Include C++ tags changes (Bertin). Change "class::func" tag into "func"
@@ -2000,6 +2523,8 @@ Autocommands:
8 Autocommand for when modified files have been found, when getting input
focus again (e.g., FileChangedFocus).
Check when: getting focus, jumping to another buffer, ...
7 Autocommand for when an option is changed. Match buffer name or option
name?
8 Autocommands should not change registers. And marks? And the jumplist?
And anything else? Add a command to save and restore these things.
8 Add autocommands, user functions and user commands to ":mkvimrc".
@@ -2029,6 +2554,7 @@ Autocommands:
*Leave - Leaving a mode (in pair with the above *Enter)
VimLeaveCheck - Before Vim decides to exit, so that it can be cancelled
when exiting isn't a good idea.
CursorHoldC - CursorHold while command-line editing
WinMoved - when windows have been moved around, e.g, ":wincmd J"
CmdUndefined - Like FuncUndefined but for user commands.
SearchPost - After doing a search command (e.g. to do "M")
@@ -2053,7 +2579,10 @@ Autocommands:
the position and number of inserted/deleted lines, so
that marks can be updated. HierAssist has patch to add
BufChangePre, BufChangePost and RevertBuf. (Shah)
WinResized - When a window has been resized
ViewChanged - triggered when the text scrolls and when the window size
changes.
WinResized - After a window has been resized
WinClose - Just before closing a window
- Write the file now and then ('autosave'):
*'autosave'* *'as'* *'noautosave'* *'noas'*
'autosave' 'aw' number (default 0)
@@ -2070,8 +2599,6 @@ Omni completion:
Should work for Java (Eclipse does this), Python, Tcl, etc.
Richard Emberson mentioned working on an interface to Java.
- Check Readline for its completion interface.
- Use ctags for other languages. Writing a file could trigger running
ctags, merging the tags of the changed file.
- Ideas from others:
http://www.wholetomato.com/
http://www.vim.org/scripts/script.php?script_id=747
@@ -2106,6 +2633,12 @@ Insert mode completion/expansion:
8 Add option to set different behavior for Insert mode completion:
- ignore/match case
- different characters than 'iskeyword'
8 Add option 'isexpand', containing characters when doing expansion (so that
"." and "\" can be included, without changing 'iskeyword'). (Goldfarb)
Also: 'istagword': characters used for CTRL-].
When 'isexpand' or 'istagword' are empty, use 'iskeyword'.
Alternative: Use a pattern so that start and end of a keyword can be
defined, only allow dash in the middle, etc.
8 Add a command to undo the completion, go back to the original text.
7 Completion of an abbreviation: Can leave letters out, like what Instant
text does: www.textware.com
@@ -2136,10 +2669,6 @@ Insert mode completion/expansion:
- CTRL-X CTRL-F: Use 'path' to find completions.
- CTRL-X CTRL-F: Option to use forward slashes on MS-Windows?
- CTRL-X CTRL-F: Don't replace "$VIM" with the actual value. (Kelly)
8 Add option 'isexpand', containing characters when doing expansion (so that
"." and "\" can be included, without changing 'iskeyword'). (Goldfarb)
Also: 'istagword': characters used for CTRL-].
When 'isexpand' or 'istagword' are empty, use 'iskeyword'.
- Allow listing all matches in some way (and picking one from the list).
@@ -2255,6 +2784,7 @@ Insert mode:
'cindent', 'smartindent':
8 Lisp indenting: "\\" confuses the indenter. (Dorai Sitaram, 2006 May 17)
8 Java: Inside an anonymous class, after an "else" or "try" the indent is
too small. (Vincent Bergbauer)
Problem of using {} inside (), 'cindent' doesn't work then.
@@ -2265,6 +2795,11 @@ Insert mode:
"asdf"
}
);
6 Add 'cino' flag for this function argument layout: (Spencer Collyer)
func( arg1
, arg2
, arg3
);
7 Add separate "(0" option into inside/outside a function (Zellner):
func(
int x) // indent like "(4"
@@ -2439,7 +2974,6 @@ Visual mode:
6 In non-Block mode, "I" should insert the same text in front of each line,
before the first non-blank, "gI" in column 1.
6 In non-Block mode, "A" should append the same text after each line.
6 ":'<,'>source" should read the selected lines and ":source" them.
6 When in blockwise visual selection (CTRL-V), allow cursor to be placed
right of the line. Could also allow cursor to be placed anywhere on a TAB
or other special character.
@@ -2549,7 +3083,9 @@ Incsearch:
Searching:
8 Add "g/" and "gb" to search for a pattern in the Visually selected text?
"g?" is already used for rot13.
The vis.vim script has a ":S" command that does something like this.
Can use "g/" in Normal mode, uses the '< to '> area.
Use "&/" for searching the text in the Visual area?
8 Add a mechanism for recursiveness: "\@(([^()]*\@g[^()]*)\)". \@g stands
for "go recursive here" and \@( \) marks the recursive part.
Perl does it this way:
@@ -2557,6 +3093,9 @@ Searching:
Here $paren is evaluated when it's encountered. This is like a regexp
inside a regexp. In the above terms it would be:
\@((\([^()]\|\@g\)*)\)
8 Show the progress every second. Could use the code that checks for CTRL-C
to find out how much time has passed. Or use SIGALRM. Where to show the
number?
7 Support for approximate-regexps to find similar words (agrep
http://www.tgries.de/agrep/ tre: http://laurikari.net/tre/index.html).
8 Add an item for a big character range, so that one can search for a
@@ -2661,6 +3200,13 @@ Searching:
Undo:
8 Undo tree: visually show the tree somehow (Damian Conway)
Show only the leaves, indicating how many changed from the branch and the
timestamp?
Put branch with most recent change on the left, older changes get more
indent?
8 Search for pattern in undo tree, showing when it happened and the text
state, so that you can jump to it.
- Persistent undo: store undo in a file.
Use timestamps, so that a version a certain time ago can be found and info
before some time/date can be flushed. 'undopersist' gives maximum time to
@@ -3033,8 +3579,13 @@ Various improvements:
next <li>, ]< to next </li>, [< to previous </li>.
8 Add ":rename" command: rename the file of the current buffer and rename
the buffer. Buffer may be modified.
7 Instead of filtering errors with a shell script it should be possible to
do this with Vim script. A function that filters the raw text that comes
from the 'makeprg'?
- Add %b to 'errorformat': buffer number. (Yegappan Lakshmanan / Suresh
Govindachar)
7 Add a command that goes back to the position from before jumping to the
first quickfix location. ":cbefore"?
6 In the quickfix window statusline add the command used to get the list of
errors, e.g. ":make foo", ":grep something *.c".
6 Python interface: add vim.message() function. (Michal Vitecek, 2002 Nov 5)
@@ -3047,7 +3598,6 @@ Various improvements:
to manipulate text without changing the window layout.
8 Add a command to revert to the saved version of file; undo or redo until
all changes are gone.
7 Add a ":cpfile", go in the other direction as ":cnfile".
6 "vim -q -" should read the list of errors from stdin. (Gautam Mudunuri)
8 Add "--remote-fail": When contacting the server fails, exit Vim.
Add "--remote-self": When contacting the server fails, do it in this Vim.
@@ -3068,7 +3618,6 @@ Various improvements:
etc. Combinations of Alt, Ctrl and Shift are also possible. Recognize
these to avoid inserting the raw byte sequence, handle like the key
without modifier (unless mapped).
8 Add ":breakdel *": delete all breakpoints.
7 Support ":browse edit" in console, using explorer.vim?
6 Add "gG": like what "gj" is to "j": go to the N'th window line.
8 Add command like ":normal" that accepts <Key> notation like ":map".
@@ -3107,13 +3656,6 @@ Various improvements:
7 Have a look at viH (Hellenic or Greek version of Vim). But a solution
outside of Vim might be satisfactory (Haritsis).
3 Make "2d%" work like "d%d%" instead of "d2%"?
8 Make "more" prompt accept command characters, like "hit-enter" prompt?
Or extend it with more commands, like "less": 'b' for back, 'j' for one
line down, etc.
8 For the "--more--" prompt, support the 'b'ack command for more commands.
Possible implementation: Do it at a very low level, caching the lines that
are on the screen (with highlight attributes). Avoids that changes have
to be made for all functions that list something.
7 "g CTRL-O" jumps back to last used buffer. Skip CTRL-O jumps in the same
buffer. Make jumplist remember the last ten accessed buffers?
- Keep a list of most recently used files for each window, use "[o" to go
@@ -3146,8 +3688,6 @@ Various improvements:
of the files. Only check when an event occurs (e.g., character typed,
mouse moved). Useful for non-GUI versions where keyboard focus isn't
noticeable.
9 When using ":w <fname>" it's possible that this file is loaded in another
buffer. Give a warning right away, don't wait for a shell command.
- Make 'smartcase' work even though 'ic' isn't set (Webb).
7 When formatting text, allow to break the line at a number of characters.
Use an option for this: 'breakchars'? Useful for formatting Fortran code.
@@ -3156,8 +3696,8 @@ Various improvements:
paragraphs). Complements the '2' flag. Use '>' flag when larger indent
starts a new paragraph, use '<' flag when smaller indent starts a new
paragraph. Both start a new paragraph on any indent change.
7 Add a way to define an item list with a pattern in 'formatoptions'. The
'n' flag doesn't work for "6.3" or "6a.".
8 The 'a' flag in 'formatoptions' is too dangerous. In some way only do
auto-formatting in specific regions, e.g. defined by syntax highlighting.
8 Allow using a trailing space to signal a paragraph that continues on the
next line (MIME text/plain; format=flowed, RFC 2646). Can be used for
continuous formatting. Could use 'autoformat' option, which specifies a
@@ -3358,8 +3898,6 @@ Various improvements:
- Amiga: test for 'w' flag when reading a file.
- :table command (Webb)
- Add new operator: clear, make area white (replace with spaces): "g ".
- Make it possible for a user to define a new operator. Implementation with
internal scripting language or Perl?
- Add command to ":read" a file at a certain column (blockwise read?).
- Add sort of replace mode where case is taken from the old text (Goldfarb).
- Allow multiple arguments for ":read", read all the files.

View File

@@ -1,4 +1,4 @@
*usr_01.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_01.txt* For Vim version 7.1a. Last change: 2006 Oct 08
VIM USER MANUAL - by Bram Moolenaar
@@ -57,10 +57,10 @@ installation: |usr_90.txt|.
*not-compatible*
The manuals often assume you are using Vim with Vi-compatibility switched
off. For most commands this doesn't matter, but sometimes it is important,
e.g., for multi-level undo. An easy way to make sure you are using the right
setup, copy the example vimrc file. By doing this inside Vim you don't have
to check out where it is located. How to do this depends on the system you
are using:
e.g., for multi-level undo. An easy way to make sure you are using a nice
setup is to copy the example vimrc file. By doing this inside Vim you don't
have to check out where it is located. How to do this depends on the system
you are using:
Unix: >
:!cp -i $VIMRUNTIME/vimrc_example.vim ~/.vimrc
@@ -155,7 +155,7 @@ The Vim user manual and reference manual are Copyright (c) 1988-2003 by Bram
Moolenaar. This material may be distributed only subject to the terms and
conditions set forth in the Open Publication License, v1.0 or later. The
latest version is presently available at:
http://www.opencontent.org/opl.shtml
http://www.opencontent.org/openpub/
People who contribute to the manuals must agree with the above copyright
notice.
@@ -164,8 +164,8 @@ Parts of the user manual come from the book "Vi IMproved - Vim" by Steve
Oualline (published by New Riders Publishing, ISBN: 0735710015). The Open
Publication License applies to this book. Only selected parts are included
and these have been modified (e.g., by removing the pictures, updating the
text for Vim 6.0 and fixing mistakes). The omission of the |frombook| tag
does not mean that the text does not come from the book.
text for Vim 6.0 and later, fixing mistakes). The omission of the |frombook|
tag does not mean that the text does not come from the book.
Many thanks to Steve Oualline and New Riders for creating this book and
publishing it under the OPL! It has been a great help while writing the user

View File

@@ -1,4 +1,4 @@
*usr_04.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_04.txt* For Vim version 7.1a. Last change: 2006 Jun 21
VIM USER MANUAL - by Bram Moolenaar
@@ -390,7 +390,7 @@ the clipboard in section |09.3| and here: |clipboard|.
==============================================================================
*04.8* Text objects
If the cursor is in the middle of a word and want to delete that word, you
If the cursor is in the middle of a word and you want to delete that word, you
need to move back to its start before you can do "dw". There is a simpler way
to do this: "daw".

View File

@@ -1,4 +1,4 @@
*usr_05.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_05.txt* For Vim version 7.1a. Last change: 2006 Jul 10
VIM USER MANUAL - by Bram Moolenaar
@@ -202,8 +202,8 @@ actually two parts here. "autocmd FileType text" is an autocommand. This
defines that when the file type is set to "text" the following command is
automatically executed. "setlocal textwidth=78" sets the 'textwidth' option
to 78, but only locally in one file.
>
*restore-cursor* >
autocmd BufReadPost *
\ if line("'\"") > 0 && line("'\"") <= line("$") |
\ exe "normal g`\"" |

View File

@@ -1,4 +1,4 @@
*usr_06.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_06.txt* For Vim version 7.1a. Last change: 2006 Apr 24
VIM USER MANUAL - by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*usr_07.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_07.txt* For Vim version 7.1a. Last change: 2006 Apr 24
VIM USER MANUAL - by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*usr_11.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_11.txt* For Vim version 7.1a. Last change: 2006 Apr 24
VIM USER MANUAL - by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*usr_12.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_12.txt* For Vim version 7.1a. Last change: 2006 Nov 18
VIM USER MANUAL - by Bram Moolenaar
@@ -38,8 +38,8 @@ match the start of a word: >
:%s/\<four/4/g
Obviously, this still goes wrong on "fourty". Use "\>" to match the end of a
word: >
Obviously, this still goes wrong on "fourteen". Use "\>" to match the end of
a word: >
:%s/\<four\>/4/g

View File

@@ -1,4 +1,4 @@
*usr_20.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_20.txt* For Vim version 7.1a. Last change: 2006 Apr 24
VIM USER MANUAL - by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*usr_23.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_23.txt* For Vim version 7.1a. Last change: 2006 Apr 24
VIM USER MANUAL - by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*usr_27.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_27.txt* For Vim version 7.1a. Last change: 2006 Apr 24
VIM USER MANUAL - by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*usr_28.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_28.txt* For Vim version 7.1a. Last change: 2006 Apr 24
VIM USER MANUAL - by Bram Moolenaar

View File

@@ -1,4 +1,4 @@
*usr_30.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_30.txt* For Vim version 7.1a. Last change: 2007 Apr 22
VIM USER MANUAL - by Bram Moolenaar
@@ -50,7 +50,7 @@ like this:
2 returned ~
"main.c" 11L, 111C ~
(3 of 6): too many arguments to function 'do_sub' ~
Hit ENTER or type command to continue ~
Press ENTER or type command to continue ~
From this you can see that you have errors in the file "main.c". When you
press <Enter>, Vim displays the file "main.c", with the cursor positioned on
@@ -148,7 +148,7 @@ More about these modifiers here: |filename-modifiers|.
OLD ERROR LISTS
Suppose you ":make" a program. There is an warning message in one file and an
Suppose you ":make" a program. There is a warning message in one file and an
error message in another. You fix the error and use ":make" again to check if
it was really fixed. Now you want to look at the warning message. It doesn't
show up in the last error list, since the file with the warning wasn't
@@ -242,7 +242,7 @@ form is: >
This indents the current line. Like with all operators, there are three ways
to use it. In Visual mode "=" indents the selected lines. A useful text
object is "a{". This selects the current {} block. Thus, to re-indent the
code code block the cursor is in: >
code block the cursor is in: >
=a{
@@ -315,7 +315,7 @@ In this file the output is:
filetype=help ~
This you would use "help" for {filetype}.
Thus you would use "help" for {filetype}.
For the {directory} part you need to use your runtime directory. Look at
the output of this command: >
@@ -339,7 +339,7 @@ How to do that is explained here: |indent-expression|.
The most simple 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'.
'smartindent' is not as smart as 'cindent', but smarter than 'autoindent'.
With 'smartindent' set, an extra level of indentation is added for each {
and removed for each }. An extra level of indentation will also be added for
any of the words in the 'cinwords' option. Lines that begin with # are

View File

@@ -1,4 +1,4 @@
*usr_40.txt* For Vim version 7.0. Last change: 2006 Apr 24
*usr_40.txt* For Vim version 7.1a. Last change: 2006 Jun 21
VIM USER MANUAL - by Bram Moolenaar
@@ -605,8 +605,9 @@ like "doautocmd" except it executes on all the buffers.
USING NORMAL MODE COMMANDS
The commands executed by an autocommand are Command-line command. If you want
to use a Normal mode command, the ":normal" command can be used. Example: >
The commands executed by an autocommand are Command-line commands. If you
want to use a Normal mode command, the ":normal" command can be used.
Example: >
:autocmd BufReadPost *.log normal G

View File

@@ -1,4 +1,4 @@
*various.txt* For Vim version 7.0. Last change: 2006 Apr 25
*various.txt* For Vim version 7.1a. Last change: 2007 Jan 14
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -121,6 +121,12 @@ g8 Print the hex values of the bytes used in the
:[range]# [count] [flags]
synonym for :number.
*:#!*
:#!{anything} Ignored, so that you can start a Vim script with: >
#!/usr/bin/env vim -S
echo "this is a Vim script"
quit
<
*:z* *E144*
:{range}z[+-^.=]{count} Display several lines of text surrounding the line
specified with {range}, or around the current line
@@ -163,6 +169,7 @@ g8 Print the hex values of the bytes used in the
it possible to execute Normal mode commands typed on
the command-line. {commands} is executed like it is
typed. For undo all commands are undone together.
Execution stops when an error is encountered.
If the [!] is given, mappings will not be used.
{commands} should be a complete command. If
{commands} does not finish a command, the last one
@@ -377,7 +384,7 @@ m *+tcl/dyn* Tcl interface |tcl-dynamic| |/dyn|
N *+termresponse* support for |t_RV| and |v:termresponse|
N *+textobjects* |text-objects| selection
*+tgetent* non-Unix only: able to use external termcap
N *+title* Setting the window title |'title'|
N *+title* Setting the window 'title' and 'icon'
N *+toolbar* |gui-toolbar|
N *+user_commands* User-defined commands. |user-commands|
N *+viminfo* |'viminfo'|
@@ -434,10 +441,14 @@ N *+X11* Unix only: can restore window title |X11|
after the register name can be omitted. {not in Vi}
:redi[r] @{a-z}>> Append messages to register {a-z}. {not in Vi}
:redi[r] @*> Redirect messages to the clipboard. For backward
compatibility, the ">" after the register name can be
omitted. {not in Vi}
:redi[r] @*>> Append messages to the clipboard. {not in Vi}
:redi[r] @*>
:redi[r] @+> Redirect messages to the selection or clipboard. For
backward compatibility, the ">" after the register
name can be omitted. See |quotestar| and |quoteplus|.
{not in Vi}
:redi[r] @*>>
:redi[r] @+>> Append messages to the selection or clipboard.
{not in Vi}
:redi[r] @"> Redirect messages to the unnamed register. For
backward compatibility, the ">" after the register
@@ -447,6 +458,7 @@ N *+X11* Unix only: can restore window title |X11|
:redi[r] => {var} Redirect messages to a variable. If the variable
doesn't exist, then it is created. If the variable
exists, then it is initialized to an empty string.
The variable will remain empty until redirection ends.
Only string variables can be used. After the
redirection starts, if the variable is removed or
locked or the variable type is changed, then further

File diff suppressed because it is too large Load Diff

View File

@@ -1,4 +1,4 @@
*workshop.txt* For Vim version 7.0. Last change: 2006 Apr 24
*workshop.txt* For Vim version 7.1a. Last change: 2006 Apr 24
VIM REFERENCE MANUAL by Gordon Prieur

View File

@@ -226,7 +226,7 @@ Stampa 3 linee (0x30 bytes esadecimali) alla fine di
\fI% xxd \-s \-0x30 file
.PP
.br
Stampa 120 bytes come immagine esadecimale continua con 40 bytes per linea.
Stampa 120 bytes come immagine esadecimale continua con 20 bytes per linea.
.br
\fI% xxd \-l 120 \-ps \-c 20 xxd.1\fR

View File

@@ -231,7 +231,7 @@ xxd
.PP
.br
Вывести 120 байтов в виде непрерывного шестнадцатеричного представления
по 40 октетов в строке:
по 20 октетов в строке:
.PP
\fI% xxd \-l 120 \-ps \-c 20 xxd.1\fR
.br

View File

@@ -123,7 +123,7 @@ added to file positions found in hexdump.
start at
.RI < seek >
bytes abs. (or rel.) infile offset.
\fI+ fRindicates that the seek is relative to the current stdin file position
\fI+ \fRindicates that the seek is relative to the current stdin file position
(meaningless when not reading from stdin). \fI\- \fRindicates that the seek
should be that many characters from the end of the input (or if combined with
\fI+\fR: before the current stdin file position).
@@ -172,17 +172,17 @@ The following examples may help to clarify (or further confuse!)...
Rewind stdin before reading; needed because the `cat' has already read to the
end of stdin.
.br
\fI% sh \-c "cat > plain_copy; xxd \-s 0 > hex_copy" < file
\fI% sh \-c "cat > plain_copy; xxd \-s 0 > hex_copy" < file\fR
.PP
Hexdump from file position 0x480 (=1024+128) onwards.
The `+' sign means "relative to the current position", thus the `128' adds to
the 1k where dd left off.
.br
\fI% sh \-c "dd of=plain_snippet bs=1k count=1; xxd \-s +128 > hex_snippet" < file
\fI% sh \-c "dd of=plain_snippet bs=1k count=1; xxd \-s +128 > hex_snippet" < file\fR
.PP
Hexdump from file position 0x100 ( = 1024\-768) on.
.br
\fI% sh \-c "dd of=plain_snippet bs=1k count=1; xxd \-s +\-768 > hex_snippet" < file
\fI% sh \-c "dd of=plain_snippet bs=1k count=1; xxd \-s +\-768 > hex_snippet" < file\fR
.PP
However, this is a rare situation and the use of `+' is rarely needed.
The author prefers to monitor the effect of xxd with strace(1) or truss(1), whenever \-s is used.
@@ -192,16 +192,16 @@ The author prefers to monitor the effect of xxd with strace(1) or truss(1), when
Print everything but the first three lines (hex 0x30 bytes) of
.BR file .
.br
\fI% xxd \-s 0x30 file
\fI% xxd \-s 0x30 file\fR
.PP
.br
Print 3 lines (hex 0x30 bytes) from the end of
.BR file .
.br
\fI% xxd \-s \-0x30 file
\fI% xxd \-s \-0x30 file\fR
.PP
.br
Print 120 bytes as continuous hexdump with 40 octets per line.
Print 120 bytes as continuous hexdump with 20 octets per line.
.br
\fI% xxd \-l 120 \-ps \-c 20 xxd.1\fR
.br