> I actually prefer wrapping. The inconsistant behaviour always annoyed
> me.
That's interesting. VED has had the asymmetry between backward and
forward search since it was put in around 1981, and this is the first
time I have ever heard anyone complain about it.
In situations when you don't know whether the thing you are looking for
is above or below your current location in the editor buffer, why do you
ever search backwards? I would have thought that having the forward
search was all you need in that context?
And what do you do now if you want to find out whether there's a
declaration of xxx earlier than the current location, a common
requirement during program development?
Previously a backward search would either take you to the earlier
occurrence, or leave you at the current location (with a "Not found
message"). Now you may end up suddenly looking at a later occurrence of
xxx, unless you take the trouble to use the cumbersome no-wrap syntax in
the search. In that case not only do you end up at an irrelevant file
location, but getting back to where you were requires effort. I'd like
to know when that really is what you want.
I think it's daft: the default should be the other way round - ie you
specify if you want to wrap in backward search, otherwise it doesn't.
Aaron
|