Hrvoje Niksic <hniksic(a)arsdigita.com> writes:
palmieri(a)math.washington.edu (John H. Palmieri) writes:
> Should find-file-compare-truenames be 't' by default instead of
> 'nil'?
Maybe. I set it to t in my .emacs. Most people probably wouldn't
care. Some people might object that it's too "intelligent", and that
it might break things in some situations.
But it seems like the right default behaviour, so I see no good reason
not to enable it by default. Is the GNU Emacs equivalent feature
configurable? If yes, is it "on" by default?
Yes and yes: there is a variable 'find-file-existing-other-name' which
has default value t.
find-file-existing-other-name
Documentation:
*Non-nil means find a file under alternative names, in existing buffers.
This means if any existing buffer is visiting the file you want
under another name, you get the existing buffer instead of a new buffer.
(Of course, the default value of t is in conflict with the GNU Emacs
documentation which says
If you visit two names for the same file, normally Emacs makes two
different buffers, but it warns you about the situation.
If you wish to avoid visiting the same file in two buffers under
different names, set the variable `find-file-existing-other-name' to a
non-`nil' value.
I'll have to submit a bug report.)
--
John H. Palmieri
Dept of Mathematics, Box 354350 palmieri(a)math.washington.edu
University of Washington
http://www.math.washington.edu/~palmieri/
Seattle, WA 98195-4350