(CC'ing the author of the patch)
Hi Bram!
On Di, 13 Apr 2010, Bram Moolenaar wrote:
> Basically:
> - look at the documentation
> - look at what the code does (fix documentation when needed)
> - test that what it's supposed to do actually works, possibly trying
> every documented feature
> - think of border cases (empty file, one very long line, missing line
> break, binary file, etc.) and test that all works
> - have a brainstorm about what could go wrong and test that (e.g.,
> changing the file with another editor, renaming another file in its
> place)
>
> Using some kind of script to make this less work. Could perhaps be a
> Vim script that writes a script file and runs another Vim with "!vim -S
> scriptfile filename". That way it's portable.
Thanks for letting me know. Today it's the first time I tested this
feature. This is really awesome and I have been missing it so much. I
already started testing it. There are some issues I already noticed:
1) This does not work very well with files that are symlinked. If
you start by editing a symlink file, the undo will be saved and
remembered only for the symlink. If you are later start editing
the symlink target, there won't be any undo-state remembered and
further you are loosing your old remembered undo points (because
even if you later again start editing the symlink file, you
won't be able to undo changes.
2) What happens with old undo files? They seem to accumulate and
it seems that sooner or later you'll have in ~/.vim/undo/ a bunch
of unusable undo files. Could they be deleted automatically,
when they become unusable or is there a way to force reading the
undo-file?
3) :rundo should at least output some message, if it can't restore
the undo points from a previous session, since the file has been
modified by some other program.
I'll keep on testing it.
regards,
Christian
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
