summaryrefslogtreecommitdiff
path: root/runtime/doc
diff options
context:
space:
mode:
Diffstat (limited to 'runtime/doc')
-rw-r--r--runtime/doc/autocmd.txt7
-rw-r--r--runtime/doc/diff.txt6
-rw-r--r--runtime/doc/indent.txt4
-rw-r--r--runtime/doc/map.txt5
-rw-r--r--runtime/doc/options.txt9
-rw-r--r--runtime/doc/pattern.txt9
-rw-r--r--runtime/doc/syntax.txt45
-rw-r--r--runtime/doc/todo.txt53
8 files changed, 94 insertions, 44 deletions
diff --git a/runtime/doc/autocmd.txt b/runtime/doc/autocmd.txt
index c129e3fc8..d40df2341 100644
--- a/runtime/doc/autocmd.txt
+++ b/runtime/doc/autocmd.txt
@@ -1,4 +1,4 @@
-*autocmd.txt* For Vim version 7.3. Last change: 2010 Jul 22
+*autocmd.txt* For Vim version 7.3. Last change: 2011 Apr 26
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -786,7 +786,10 @@ TermChanged After the value of 'term' has changed. Useful
TermResponse After the response to |t_RV| is received from
the terminal. The value of |v:termresponse|
can be used to do things depending on the
- terminal version.
+ terminal version. Note that this event may be
+ triggered halfway executing another event,
+ especially if file I/O, a shell command or
+ anything else that takes time is involved.
*User*
User Never executed automatically. To be used for
autocommands that are only executed with
diff --git a/runtime/doc/diff.txt b/runtime/doc/diff.txt
index 01767f905..288ddd78a 100644
--- a/runtime/doc/diff.txt
+++ b/runtime/doc/diff.txt
@@ -1,4 +1,4 @@
-*diff.txt* For Vim version 7.3. Last change: 2010 Dec 08
+*diff.txt* For Vim version 7.3. Last change: 2011 Apr 14
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -167,8 +167,8 @@ in diff mode in one window and "normal" in another window. It is also
possible to view the changes you have made to a buffer since the file was
loaded. Since Vim doesn't allow having two buffers for the same file, you
need another buffer. This command is useful: >
- command DiffOrig vert new | set bt=nofile | r # | 0d_ | diffthis
- \ | wincmd p | diffthis
+ command DiffOrig vert new | set bt=nofile | r ++edit # | 0d_
+ \ | diffthis | wincmd p | diffthis
(this is in |vimrc_example.vim|). Use ":DiffOrig" to see the differences
between the current buffer and the file it was loaded from.
diff --git a/runtime/doc/indent.txt b/runtime/doc/indent.txt
index 3e06aaacf..405c3dd8b 100644
--- a/runtime/doc/indent.txt
+++ b/runtime/doc/indent.txt
@@ -1,4 +1,4 @@
-*indent.txt* For Vim version 7.3. Last change: 2011 Mar 18
+*indent.txt* For Vim version 7.3. Last change: 2011 Apr 25
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -472,6 +472,8 @@ assume a 'shiftwidth' of 4.
*N Vim searches for unclosed comments at most N lines away. This
limits the time needed to search for the start of a comment.
+ If your /* */ comments stop indenting afer N lines this is the
+ value you will want to change.
(default 70 lines).
#N When N is non-zero recognize shell/Perl comments, starting with
diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt
index c18eed104..29b9e9f35 100644
--- a/runtime/doc/map.txt
+++ b/runtime/doc/map.txt
@@ -1,4 +1,4 @@
-*map.txt* For Vim version 7.3. Last change: 2010 Nov 10
+*map.txt* For Vim version 7.3. Last change: 2011 Apr 13
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -1291,7 +1291,8 @@ Possible attributes are:
-range Range allowed, default is current line
-range=% Range allowed, default is whole file (1,$)
-range=N A count (default N) which is specified in the line
- number position (like |:split|)
+ number position (like |:split|); allows for zero line
+ number.
-count=N A count (default N) which is specified either in the line
number position, or as an initial argument (like |:Next|).
Specifying -count (without a default) acts like -count=0
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 166c0aaad..a367e06b7 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -1,4 +1,4 @@
-*options.txt* For Vim version 7.3. Last change: 2011 Mar 22
+*options.txt* For Vim version 7.3. Last change: 2011 Apr 15
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -5907,9 +5907,10 @@ A jump table for the options with a short description can be found at |Q_op|.
For Unix the default it "| tee". The stdout of the compiler is saved
in a file and echoed to the screen. If the 'shell' option is "csh" or
"tcsh" after initializations, the default becomes "|& tee". If the
- 'shell' option is "sh", "ksh", "zsh" or "bash" the default becomes
- "2>&1| tee". This means that stderr is also included. Before using
- the 'shell' option a path is removed, thus "/bin/sh" uses "sh".
+ 'shell' option is "sh", "ksh", "mksh", "pdksh", "zsh" or "bash" the
+ default becomes "2>&1| tee". This means that stderr is also included.
+ Before using the 'shell' option a path is removed, thus "/bin/sh" uses
+ "sh".
The initialization of this option is done after reading the ".vimrc"
and the other initializations, so that when the 'shell' option is set
there, the 'shellpipe' option changes automatically, unless it was
diff --git a/runtime/doc/pattern.txt b/runtime/doc/pattern.txt
index 0fd31d658..84cd7360a 100644
--- a/runtime/doc/pattern.txt
+++ b/runtime/doc/pattern.txt
@@ -1,4 +1,4 @@
-*pattern.txt* For Vim version 7.3. Last change: 2011 Feb 25
+*pattern.txt* For Vim version 7.3. Last change: 2011 Apr 28
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -651,6 +651,13 @@ overview.
"foobar" you could use "\(foo\)\@!...bar", but that doesn't match a
bar at the start of a line. Use "\(foo\)\@<!bar".
+ Useful example: to find "foo" in a line that does not contain "bar": >
+ /^\%(.*bar\)\@!.*\zsfoo
+< This pattern first checks that there is not a single position in the
+ line where "bar" matches. If ".*bar" matches somewhere the \@! will
+ reject the pattern. When there is no match any "foo" will be found.
+ The "\zs" is to have the match start just before "foo".
+
*/\@<=*
\@<= Matches with zero width if the preceding atom matches just before what
follows. |/zero-width| {not in Vi}
diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt
index 6c3927410..c30926715 100644
--- a/runtime/doc/syntax.txt
+++ b/runtime/doc/syntax.txt
@@ -1,4 +1,4 @@
-*syntax.txt* For Vim version 7.3. Last change: 2011 Apr 01
+*syntax.txt* For Vim version 7.3. Last change: 2011 Apr 06
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -468,18 +468,28 @@ disabled javascript to view closed folds. To use this option, use: >
Setting html_no_foldcolumn with html_dynamic_folds will automatically set
html_hover_unfold, because otherwise the folds wouldn't be dynamic.
-By default "<pre>" and "</pre>" is used around the text. This makes it show
-up as you see it in Vim, but without wrapping. If you prefer wrapping, at the
-risk of making some things look a bit different, use: >
+By default "<pre>" and "</pre>" are used around the text. When 'wrap' is set
+in the window being converted, the CSS 2.0 "white-space:pre-wrap" value is
+used to wrap the text. You can explicitly enable the wrapping with: >
+ :let g:html_pre_wrap = 1
+or disable with >
+ :let g:html_pre_wrap = 0
+This generates HTML that looks very close to the Vim window, but unfortunately
+there can be minor differences such as the lack of a 'showbreak' option in in
+the HTML, or where line breaks can occur.
+
+Another way to obtain text wrapping in the HTML, at the risk of making some
+things look even more different, is to use: >
:let g:html_no_pre = 1
This will use <br> at the end of each line and use "&nbsp;" for repeated
-spaces.
+spaces. Doing it this way is more compatible with old browsers, but modern
+browsers support the "white-space" method.
-If you do use the "<pre>" tags, <Tab> characters in the text are included in
-the generated output if they will have no effect on the appearance of the
-text and it looks like they are in the document intentionally. This allows for
-the HTML output to be copied and pasted from a browser without losing the
-actual whitespace used in the document.
+If you do stick with the default "<pre>" tags, <Tab> characters in the text
+are included in the generated output if they will have no effect on the
+appearance of the text and it looks like they are in the document
+intentionally. This allows for the HTML output to be copied and pasted from a
+browser without losing the actual whitespace used in the document.
Specifically, <Tab> characters will be included if the 'tabstop' option is set
to the default of 8, 'expandtab' is not set, and if neither the foldcolumn nor
@@ -502,13 +512,14 @@ inserted lines as with the side-by-side diff, use: >
:let g:html_whole_filler = 1
And to go back to displaying up to three lines again: >
:unlet g:html_whole_filler
-<
-TOhtml uses the current value of 'fileencoding' if set, or 'encoding' if not,
-to determine the charset and 'fileencoding' of the HTML file. In general, this
-works for the encodings mentioned specifically by name in |encoding-names|, but
-TOhtml will only automatically use those encodings which are widely supported.
-However, you can override this to support specific encodings that may not be
-automatically detected by default.
+
+For most buffers, TOhtml uses the current value of 'fileencoding' if set, or
+'encoding' if not, to determine the charset and 'fileencoding' of the HTML
+file. 'encoding' is always used for certain 'buftype' values. In general, this
+works for the encodings mentioned specifically by name in |encoding-names|,
+but TOhtml will only automatically use those encodings which are widely
+supported. However, you can override this to support specific encodings that
+may not be automatically detected by default.
To overrule all automatic charset detection, set g:html_use_encoding to the
name of the charset to be used. TOhtml will try to determine the appropriate
diff --git a/runtime/doc/todo.txt b/runtime/doc/todo.txt
index f7a96b616..3adc36cc2 100644
--- a/runtime/doc/todo.txt
+++ b/runtime/doc/todo.txt
@@ -1,4 +1,4 @@
-*todo.txt* For Vim version 7.3. Last change: 2011 Apr 01
+*todo.txt* For Vim version 7.3. Last change: 2011 Apr 28
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -30,14 +30,11 @@ be worked on, but only if you sponsor Vim development. See |sponsor|.
*known-bugs*
-------------------- Known bugs and current work -----------------------
-Improvement patch for filetype.vim. (Thilo Six, 2011 Mar 19)
+Go through more coverity reports.
-Patch to recognize more files as log files. (Mathieu Parent, 2011 Jan 14)
+Patch for behavior of :cwindow. (Ingo Karkat, 2011 Apr 15)
-Two patches for xxd. (Florian Zumbiehl, 2011 Jan 11)
-Two updates for second one Jan 12.
-
-Go through new coverity reports.
+Configure fix for finding exctags. (Hong Xu, 2011 Aprl 2)
When 'colorcolumn' is set locally to a window, ":new" opens a window with the
same highlighting but 'colorcolumn' is empty. (Tyru, 2010 Nov 15)
@@ -45,11 +42,30 @@ Patch by Christian Brabandt, 2011 Feb 13 (but move further down).
Patch for configure related to Ruby on Mac OS X. (Bjorn Winckler, 2011 Jan 14)
+Patch to make mkdir() work properly for different encodings. (Yukihiro
+Nakadaira, 2011 Apr 23)
+
+Updated PHP syntax file. (Jason Woofenden, 2011 Apr 22)
+
+ASCII Vim logo's (Erling Westenvik, 2011 Apr 19) Add to website.
+
+Crash in autocomplete, valgrind log. (Greg Weber, 2011 Apr 22)
+
+Patch for static code analysis errors in riscOS. (Dominique Pelle, 2010 Dec 3)
+
Patch to set v:register on startup. (Ingo Karkat, 2011 Jan 16)
+Risc OS gui has obvious errors. Drop it?
+
Patch to set v:register default depending on "unnamed" in 'clipboard'. (Ingo
Karkat, 2011 Jan 16)
+Patch to add 'cscoperelative'. (Raghavendra Prabhu, 2011 Apr 18)
+
+New syntax file for dnsmasq. (Thilo Six, 2011 Apr 18)
+
+Discussion about canonicalization of Hebrew. (Ron Aaron, 2011 April 10)
+
Patch for:
InsertCharPre - user typed character Insert mode, before inserting the
char. Pattern is matched with text before the cursor.
@@ -119,6 +135,21 @@ only one of the two ends gets the cchar displayed. (Brett Stahlman, 2010 Aug
Bug in repeating Visual "u". (Lawrence Kesteloot, 2010 Dec 20)
+In GTK Gvim, setting 'lines' and 'columns' to 99999 causes a crash (Tony
+Mechelynck, 2011 Apr 25). Can reproduce the crash sometimes:
+ gvim -N -u NONE --cmd 'set lines=99999 columns=99999'
+(gvim:25968): Gdk-WARNING **: Native Windows wider or taller than 65535 pixels are not supported
+The program 'gvim' received an X Window System error.
+This probably reflects a bug in the program.
+The error was 'RenderBadPicture (invalid Picture parameter)'.
+ (Details: serial 313 error_code 161 request_code 149 minor_code 8)
+ (Note to programmers: normally, X errors are reported asynchronously;
+ that is, you will receive the error a while after causing it.
+ To debug your program, run it with the --sync command line
+ option to change this behavior. You can then get a meaningful
+ backtrace from your debugger if you break on the gdk_x_error() function.)
+Check that number of pixels doesn't go above 65535?
+
CursorHold repeats typed key when it's the start of a mapping.
(Will Gray, 2011 Mar 23)
@@ -204,8 +235,6 @@ Version of netbeans.c for use with MacVim. (Kazuki Sakamoto, 2010 Nov 18)
there is one backslash. (Ray Frush, 2010 Nov 18) What does the original ex
do?
-":find" completion does not escape space in directory name. (Isz, 2010 Nov 2)
-
Searching mixed with Visual mode doesn't redraw properly. (James Vega, 2010 Nov
22)
@@ -411,8 +440,6 @@ Undo problem: line not removed as expected when using setline() from Insert
mode. (Israel Chauca, 2010 May 13, more in second msg)
Break undo when CTRL-R = changes the text? Or save more lines?
-Patch for static code analysis errors in riscOS. (Dominique Pelle, 2010 Dec 3)
-
Patch for better #if 0 syntax highlighting for C code. (Ben Schmidt, 2011 Jan
20)
@@ -1402,9 +1429,6 @@ In gvim the backspace key produces a backspace character, but on Linux the
VERASE key is Delete. Set VERASE to Backspace? (patch by Stephane Chazelas,
2007 Oct 16)
-When entering a C /* comment, after typing <Enter> for 70 times the indent
-disappears. (Vincent Beffara, 2008 Jul 3)
-
TermResponse autocommand isn't always triggered when using vimdiff. (Aron
Griffis, 2007 Sep 19)
@@ -3768,6 +3792,7 @@ Insert mode:
7 Use CTRL-G <count> to repeat what follows. Useful for inserting a
character multiple times or repeating CTRL-Y.
- Make 'revins' work in Replace mode.
+9 Can't use multi-byte characters for 'matchpairs'.
7 Use 'matchpairs' for 'showmatch': When inserting a character check if it
appears in the rhs of 'matchpairs'.
- In Insert mode (and command line editing?): Allow undo of the last typed