-*todo.txt* For Vim version 7.0aa. Last change: 2005 Jan 25
+*todo.txt* For Vim version 7.0aa. Last change: 2005 Jan 27
VIM REFERENCE MANUAL by Bram Moolenaar
*known-bugs*
-------------------- Known bugs and current work -----------------------
-Searching backwards with \zs gets stuck. (Brett Stahlman, Jan 23)
+Allow space: "call function ()"
-netrw plugin: "i" remembers last action but not per window.
+List a:000 must be immutable.
+ lock(list) lock(dict)
+ deeplock(list)
+ islocked(list)
+Also unlock(), so that you can pass a list to a function and be sure it's not
+changed? Then super-lock a:000, can't be unlocked.
+
+":breakadd here" doesn't work. (Johnny Blaze, Jan 26)
+Problem with backslashes in file name?
List data type performance:
- Cache the length of a List?
- Go through the code for magic braces.
- Check use of v_type for VAR_FUNC, VAR_LIST ad VAR_DICT.
-Mention Rsync command on runtime.php page:
+Mention rsync command on runtime.php page:
rsync -avzcP --delete --exclude="dos" --delete-excluded ftp.nluug.nl::Vim/runtime/ vim63-runtime
-netrw plugin:
-- provide :Explore and :Sexplore like the old file explorer?
-- alignment of long listing isn't very good.
-
Better way to get temp file for tcltags and vimspell scripts. (javier Pena)
Possibly leave out code for temp directory.
Add gui_mch_browsedir() for Motif, KDE and Mac OS/X.
HTML indenting can be slow, find out why. Any way to do some kind of
-profiling for Vim script?
+profiling for Vim script? At least add a function to get the current time in
+usec. reltime([start, [end]])
+ reltime().sec == seconds, reltime().usec = microseconds
+ reltime(start) current time relative to [start]
+ echo timestring(reltime(start), 3) (3 is nr of digits after dot)
+ reltime(start, end) difference between start and end
Updated Ruby interface. (Ryan Paul)
-*version7.txt* For Vim version 7.0aa. Last change: 2005 Jan 25
+*version7.txt* For Vim version 7.0aa. Last change: 2005 Jan 26
VIM REFERENCE MANUAL by Bram Moolenaar
Welcome to Vim 7! A large number of features has been added. This file
mentions all the new items, changes to existing features and bug fixes
-compared to Vim 6.x.
+compared to Vim 6.x. Use this command to see the version you are using: >
+ :version
See |vi_diff.txt| for an overview of differences between Vi and Vim 7.0.
See |version4.txt| for differences between Vim 3.x and Vim 4.x.
INCOMPATIBLE CHANGES *incompatible-7*
These changes are incompatible with previous releases. Check this list if you
-run into a problem when upgrading from Vim 6.x to 7.0
+run into a problem when upgrading from Vim 6.x to 7.0.
+
+A ":write file" command no longer resets the 'modified' flag of the buffer,
+unless the '+' flag is in 'cpoptions' |cpo-+|. This was illogical, since the
+buffer is still modified compared to the original file. And when undoing
+all changes the file would actually be marked modified. It does mean that
+":quit" fails now.
":helpgrep" now uses a help window to display a match.
:next foo\"888 'foo888' 'foo"888'
:next a\"b c\"d 'ab cd' 'a"b' and 'c"d'
-A ":write file" command no longer resets the 'modified' flag of the buffer,
-unless the '+' flag is in 'cpoptions' |cpo-+|. This was illogical, since the
-buffer is still modified compared to the original file. And when undoing
-all changes the file would actually be marked modified. It does mean that
-":quit" fails now.
-
In a |literal-string| a single quote can be doubled to get one.
":echo 'a''b'" would result in "a b", but now that two quotes stand for one it
results in "a'b".
Configure could not handle "-Dfoo=long\ long" in the TCL config output.
+When searching backwards, using a pattern that matches a newline and uses \zs
+after that, didn't find a match. Could also get a hang or end up in the right
+column in the wrong line.
+
vim:tw=78:ts=8:ft=help:norl: