Am I the only person who is being driven mad by the fact that after
interactive search and replace you are put back to the last location at
which a change was made rather than the location at which you type "n"?
Typically that's a location at which I find there's a change I have to
do "by hand". But VED throws me back to some unrelated location where it
last made a change, and I then have to find the desired location myself,
which can be time-consuming and error prone in a large file, even though
VED was at it a moment earlier.
I would rather give up regular expression matching (since VED is
programmable anyway) than put up with this sort of thing.
Aaron
|