Re: info -f does not ignore ./

[Karl Berry]

    So how does one tell Info to find /usr/local/info/foo/bar.info when
    there's a ./foo/bar.info around?

Set INFOPATH, or say info -f /usr/local/...

    I really wish that we leave this feature alone, since I'm afraid
    changing it will break those (Debian?) systems that use subdirectories
    to support multiple versions of the same manual on the same machine,
    and possibly other valid uses of this old feature.

I don't see that it's likely to "break" any user expectations.  If there
is a ./foo/bar.info, why wouldn't you want info [-f] foo/bar to find it?
For that matter, Bruno is not the first person who has been confused by
info [-f] not finding such "local" files, so if anything, I think it'll
be a net decrease in confusion.

For something to "break", a user would have to have been in the habit of
typing info [-f] emacs-20/emacs *and* be in a directory with a
subdirectory emacs-20 containing a file emacs.info *and* that emacs.info
is the one not desired.  This seems essentially zero probability to me.

Having yet another option like --info-filename-no-path-lookup seems
pretty ugly to me.

The number of people using standalone info is vanishingly small, anyway.
We're spending too much time on this ...

k