diff options
author | Bram Moolenaar <Bram@vim.org> | 2005-09-01 20:46:49 +0000 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2005-09-01 20:46:49 +0000 |
commit | e344bead3ecc16a0982d157e8c19050f6dff4e0c (patch) | |
tree | 34da48120172b9e2efc8c559733c2b69db5a24ba /runtime | |
parent | da2303d96b0f55d30e9b5b57d3459d5e1ea22ec2 (diff) |
updated for version 7.0140v7.0140
Diffstat (limited to 'runtime')
79 files changed, 2758 insertions, 228 deletions
diff --git a/runtime/autoload/ccomplete.vim b/runtime/autoload/ccomplete.vim new file mode 100644 index 0000000000..f699ca7582 --- /dev/null +++ b/runtime/autoload/ccomplete.vim @@ -0,0 +1,32 @@ +" Vim completion script +" Language: C +" Maintainer: Bram Moolenaar <Bram@vim.org> +" Last Change: 2005 Sep 01 + +function! ccomplete#Complete(findstart, base) + if a:findstart + " locate the start of the word + let line = getline('.') + let start = col('.') - 1 + while start > 0 + if line[start - 1] =~ '\w\|\.' + let start -= 1 + elseif start > 1 && line[start - 2] == '-' && line[start - 1] == '>' + let start -= 2 + else + break + endif + endwhile + return start + endif + + " return list of matches + let items = split(a:base, '\.\|->') + if len(items) == 1 + " Only one part, no "." or "->": complete from tags file. + let diclist = taglist(items[0]) + return map(diclist, 'v:val["name"]') + endif + return items +endfunction + diff --git a/runtime/doc/Makefile b/runtime/doc/Makefile index 3aef1ca97c..a5770c2b28 100644 --- a/runtime/doc/Makefile +++ b/runtime/doc/Makefile @@ -19,6 +19,7 @@ DOCS = \ change.txt \ cmdline.txt \ debugger.txt \ + debug.txt \ develop.txt \ diff.txt \ digraph.txt \ @@ -139,6 +140,7 @@ HTMLS = \ autocmd.html \ change.html \ cmdline.html \ + debug.html \ debugger.html \ develop.html \ diff.html \ diff --git a/runtime/doc/debug.txt b/runtime/doc/debug.txt new file mode 100644 index 0000000000..a0fef1b646 --- /dev/null +++ b/runtime/doc/debug.txt @@ -0,0 +1,69 @@ +*debug.txt* For Vim version 7.0aa. Last change: 2005 Sep 01 + + + VIM REFERENCE MANUAL by Bram Moolenaar + + +Debugging Vim *debug-vim* + +This is for debugging Vim itself, when it doesn't work properly. + +1. Location of a crash, using gcc and gdb |debug-gcc| +2. Windows Bug Reporting |debug-win32| + +============================================================================== + +1. Location of a crash, using gcc and gdb *debug-gcc* + +When Vim crashes in one of the test files, and you are using gcc for +compilation, here is what you can do to find out exactly where Vim crashes. +This also applies when using the MingW tools. + +1. Compile Vim with the "-g" option (there is a line in the Makefile for this, + which you can uncomment). + +2. Execute these commands (replace "11" with the test that fails): > + cd testdir + gdb ../vim + run -u unix.vim -U NONE -s dotest.in test11.in + +3. Check where Vim crashes, gdb should give a message for this. + +4. Get a stack trace from gdb with this command: > + where +< You can check out different places in the stack trace with: > + frame 3 +< Replace "3" with one of the numbers in the stack trace. + +============================================================================== + +2. Windows Bug Reporting *debug-win32* + +If the Windows version of Vim crashes in a reproducible manner, +you can take some steps to provide a useful bug report. + +First, you must obtain the debugger symbols (PDB) file for your executable: +gvim.pdb for gvim.exe, or vim.pdb for vim.exe. It should be available +from the same place that you obtained the executable. Be sure to use +the PDB that matches the EXE. + +If you built the executable yourself with the Microsoft Visual C++ compiler, +then the PDB was built with the EXE. + +You can download the Microsoft Visual C++ Toolkit from + http://msdn.microsoft.com/visualc/vctoolkit2003/ +This contains the command-line tools, but not the Visual Studio IDE. + +The Debugging Tools for Windows can be downloaded from + http://www.microsoft.com/whdc/devtools/debugging/default.mspx +This includes the WinDbg debugger. + +If you have Visual Studio, use that instead of the VC Toolkit +and WinDbg. + + +(No idea what to do if your binary was built with the Borland or Cygwin +compilers. Sorry.) + +========================================================================= + vim:tw=78:ts=8:ft=help:norl: diff --git a/runtime/doc/develop.txt b/runtime/doc/develop.txt index a640f5b3be..498833c5a7 100644 --- a/runtime/doc/develop.txt +++ b/runtime/doc/develop.txt @@ -1,4 +1,4 @@ -*develop.txt* For Vim version 7.0aa. Last change: 2005 Aug 14 +*develop.txt* For Vim version 7.0aa. Last change: 2005 Sep 01 VIM REFERENCE MANUAL by Bram Moolenaar @@ -238,8 +238,8 @@ get_env_value() Linux system function VARIOUS *style-various* -Typedef'ed names should end in "_t": > - typedef int some_t; +Typedef'ed names should end in "_T": > + typedef int some_T; Define'ed names should be uppercase: > #define SOME_THING Features always start with "FEAT_": > diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt index b412734e6f..bc03f03aae 100644 --- a/runtime/doc/eval.txt +++ b/runtime/doc/eval.txt @@ -1,4 +1,4 @@ -*eval.txt* For Vim version 7.0aa. Last change: 2005 Aug 23 +*eval.txt* For Vim version 7.0aa. Last change: 2005 Aug 31 VIM REFERENCE MANUAL by Bram Moolenaar @@ -4081,12 +4081,12 @@ string({expr}) Return {expr} converted to a String. If {expr} is a Number, *strlen()* strlen({expr}) The result is a Number, which is the length of the String - {expr} in bytes. If you want to count the number of - multi-byte characters use something like this: > + {expr} in bytes. + If you want to count the number of multi-byte characters (not + counting composing characters) use something like this: > :let len = strlen(substitute(str, ".", "x", "g")) - -< Composing characters are not counted. +< If the argument is a Number it is first converted to a String. For other types an error is given. Also see |len()|. diff --git a/runtime/doc/help.txt b/runtime/doc/help.txt index 2007a8af81..5fa8cf1e4a 100644 --- a/runtime/doc/help.txt +++ b/runtime/doc/help.txt @@ -1,4 +1,4 @@ -*help.txt* For Vim version 7.0aa. Last change: 2005 Mar 19 +*help.txt* For Vim version 7.0aa. Last change: 2005 Sep 01 VIM - main help file k @@ -97,6 +97,7 @@ General subjects ~ |quotes.txt| remarks from users of Vim |todo.txt| known problems and desired extensions |develop.txt| development of Vim +|debug.txt| debugging Vim itself |uganda.txt| Vim distribution conditions and what to do with your money Basic editing ~ diff --git a/runtime/doc/if_ruby.txt b/runtime/doc/if_ruby.txt index 3ca8cc510b..1efb6ce785 100644 --- a/runtime/doc/if_ruby.txt +++ b/runtime/doc/if_ruby.txt @@ -1,4 +1,4 @@ -*if_ruby.txt* For Vim version 7.0aa. Last change: 2005 Mar 29 +*if_ruby.txt* For Vim version 7.0aa. Last change: 2005 Aug 31 VIM REFERENCE MANUAL by Shugo Maeda @@ -159,6 +159,8 @@ Methods: buffer Returns the buffer displayed in the window. height Returns the height of the window. height = {n} Sets the window height to {n}. +width Returns the width of the window. +width = {n} Sets the window width to {n}. cursor Returns a [row, col] array for the cursor position. cursor = [{row}, {col}] Sets the cursor position to {row} and {col}. diff --git a/runtime/doc/insert.txt b/runtime/doc/insert.txt index ae90eb954c..6530d9ebfc 100644 --- a/runtime/doc/insert.txt +++ b/runtime/doc/insert.txt @@ -1,4 +1,4 @@ -*insert.txt* For Vim version 7.0aa. Last change: 2005 Aug 17 +*insert.txt* For Vim version 7.0aa. Last change: 2005 Sep 01 VIM REFERENCE MANUAL by Bram Moolenaar @@ -868,8 +868,8 @@ CTRL-X CTRL-V Guess what kind of item is in front of the cursor and User defined completion *compl-function* Completion is done by a function that can be defined by the user with the -'completefunc' option. See the option for how the function is called and an -example. +'completefunc' option. See the 'completefunc' help for how the function +is called and an example. *i_CTRL-X_CTRL-U* CTRL-X CTRL-U Guess what kind of item is in front of the cursor and @@ -884,7 +884,10 @@ CTRL-X CTRL-U Guess what kind of item is in front of the cursor and Occult completion *compl-occult* -Completion is done by a supernatural being. +Completion is done by a function that can be defined by the user with the +'occultfunc' option. This is to be used for filetype-specific completion. + +See the 'completefunc' help for how the function is called and an example. *i_CTRL-X_CTRL-O* CTRL-X CTRL-O Guess what kind of item is in front of the cursor and diff --git a/runtime/doc/intro.txt b/runtime/doc/intro.txt index 3f8e35d5b5..89f020c507 100644 --- a/runtime/doc/intro.txt +++ b/runtime/doc/intro.txt @@ -1,4 +1,4 @@ -*intro.txt* For Vim version 7.0aa. Last change: 2005 Jun 12 +*intro.txt* For Vim version 7.0aa. Last change: 2005 Sep 01 VIM REFERENCE MANUAL by Bram Moolenaar @@ -151,31 +151,19 @@ example and try to find out which settings or other things influence the appearance of the bug. Try different machines, if possible. Send me patches if you can! -In case of doubt, use: > +It will help to include information about the version of Vim you are using and +your setup. You can get the information with this command: > :so $VIMRUNTIME/bugreport.vim This will create a file "bugreport.txt" in the current directory, with a lot of information of your environment. Before sending this out, check if it doesn't contain any confidential information! - *debug-vim* -When Vim crashes in one of the test files, and you are using gcc for -compilation, here is what you can do to find out exactly where Vim crashes: +If Vim crashes, please try to find out where. You can find help on this here: +|debug.txt|. -1. Compile Vim with the "-g" option (there is a line in the Makefile for this, - which you can uncomment). - -2. Execute these commands (replace "11" with the test that fails): > - cd testdir - gdb ../vim - run -u unix.vim -U NONE -s dotest.in test11.in - -3. Check where Vim crashes, gdb should give a message for this. - -4. Get a stack trace from gdb with this command: > - where -< You can check out different places in the stack trace with: > - frame 3 -< Replace "3" with one of the numbers in the stack trace. +In case of doubt or when you wonder if the problem has already been fixed but +you can't find a fix for it, become a member of the vim-dev maillist and ask +your question there. |maillist| *year-2000* *Y2K* Since Vim internally doesn't use dates for editing, there is no year 2000 diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt index 5fb03e9165..c33023a75e 100644 --- a/runtime/doc/map.txt +++ b/runtime/doc/map.txt @@ -666,6 +666,16 @@ used in a |filetype-plugin| file. Example for a C plugin file: > mode, '!' for both. These are the same as for mappings, see |map-listing|. + *:abbreviate-verbose* +When 'verbose' is non-zero, listing an abbreviation will also display where it +was last defined. Example: > + + :verbose abbreviate + ! teh the + Last set from /home/abcd/vim/abbr.vim + +See |:verbose-cmd| for more information. + :ab[breviate] {lhs} list the abbreviations that start with {lhs} You may need to insert a CTRL-V (type it twice) to avoid that a typed {lhs} is expanded, since diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt index eb5a34a4da..20d0e9f169 100644 --- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -1,4 +1,4 @@ -*options.txt* For Vim version 7.0aa. Last change: 2005 Aug 27 +*options.txt* For Vim version 7.0aa. Last change: 2005 Sep 01 VIM REFERENCE MANUAL by Bram Moolenaar @@ -1591,23 +1591,29 @@ A jump table for the options with a short description can be found at |Q_op|. This option specifies a function to be used for CTRL-X CTRL-U completion. |i_CTRL-X_CTRL-U| - The function will be invoked with three arguments: - a:findstart either 1 or 0 - a:col column in the cursor line where the completion ends, - first column is zero - a:base the text with which matches should match + The function will be invoked with two arguments. First the function + is called to find the start of the text to be completed. Secondly the + function is called to actually find the matches. - When the a:findstart argument is 1, the function must return the - column of where the completion starts. It must be a number between - zero and "a:col". This involves looking at the characters in the - cursor line before column a:col and include those characters that - could be part of the completed item. The text between this column and - a:col will be replaced with the matches. Return -1 if no completion - can be done. + On the first invocation the arguments are: + a:findstart 1 + a:base empty - When the a:findstart argument is 0 the function must return a List - with the matching words. These matches should include the "a:base" - text. When there are no matches return an empty List. + The function must return the column of where the completion starts. + It must be a number between zero and the cursor column "col('.')". + This involves looking at the characters just before the cursor and + including those characters that could be part of the completed item. + The text between this column and the cursor column will be replaced + with the matches. Return -1 if no completion can be done. + + On the second invocation the arguments are: + a:findstart 0 + a:base the text with which matches should match, what was + located in the first call + + The function must return a List with the matching words. These + matches usually include the "a:base" text. When there are no matches + return an empty List. When searching for matches takes some time call |complete_add()| to add each match to the total list. These matches should then not @@ -1615,16 +1621,16 @@ A jump table for the options with a short description can be found at |Q_op|. allow the user to press a key while still searching for matches. Stop searching when it returns non-zero. - The function must not move the cursor! + The function may move the cursor, it is restored afterwards. This option cannot be set from a |modeline| or in the |sandbox|, for security reasons. An example that completes the names of the months: > - fun! CompleteMonths(findstart, col, base) + fun! CompleteMonths(findstart, base) if a:findstart " locate the start of the word let line = getline('.') - let start = a:col + let start = col('.') - 1 while start > 0 && line[start - 1] =~ '\a' let start -= 1 endwhile @@ -1643,11 +1649,11 @@ A jump table for the options with a short description can be found at |Q_op|. set completefunc=CompleteMonths < The same, but now pretending searching for matches is slow: > - fun! CompleteMonths(findstart, col, base) + fun! CompleteMonths(findstart, base) if a:findstart " locate the start of the word let line = getline('.') - let start = a:col + let start = col('.') - 1 while start > 0 && line[start - 1] =~ '\a' let start -= 1 endwhile @@ -4588,6 +4594,18 @@ A jump table for the options with a short description can be found at |Q_op|. The minimum value is 1, the maximum value is 10. NOTE: 'numberwidth' is reset to 8 when 'compatible' is set. + *'occultfunc'* *'ofu'* +'occultfunc' 'ofu' string (default: empty) + local to buffer + {not in Vi} + {not available when compiled without the +eval + or +insert_expand feature} + This option specifies a function to be used for CTRL-X CTRL-O + completion. |i_CTRL-X_CTRL-O| + |