* Bug with find-file-existing-other-name option
@ 2004-12-22 11:51 Richard Skinner
0 siblings, 0 replies; 2+ messages in thread
From: Richard Skinner @ 2004-12-22 11:51 UTC (permalink / raw)
When this option is turned on it mis-identifies files which have the
same content/size/timestamp/flags as the 'same' file. I am using a build
system which exports build header files using 'cp' to another directory.
When gcc reports an error in an exported header and I use emacs to goto
that error point the exported header is opened as expected. Attempting
to then open the actual source header so that it can be edited causes
emacs to claim that the two files are the same and it refuses to open
the proper file.
These two files are clearly not the same file - they are stored on
separate inodes and are not links of any sort.
Turning find-file-existing-other-name off stops this behaviour but then
loses the desirable behaviour of preventing the same file accessed by 2
different paths being opened twice.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Bug with find-file-existing-other-name option
[not found] <mailman.8081.1103717102.27204.bug-gnu-emacs@gnu.org>
@ 2004-12-22 17:54 ` Kevin Rodgers
0 siblings, 0 replies; 2+ messages in thread
From: Kevin Rodgers @ 2004-12-22 17:54 UTC (permalink / raw)
Richard Skinner wrote:
> When this option is turned on it mis-identifies files which have the
> same content/size/timestamp/flags as the 'same' file. I am using a build
> system which exports build header files using 'cp' to another directory.
> When gcc reports an error in an exported header and I use emacs to goto
> that error point the exported header is opened as expected. Attempting
> to then open the actual source header so that it can be edited causes
> emacs to claim that the two files are the same and it refuses to open
> the proper file.
> These two files are clearly not the same file - they are stored on
> separate inodes and are not links of any sort.
> Turning find-file-existing-other-name off stops this behaviour but then
> loses the desirable behaviour of preventing the same file accessed by 2
> different paths being opened twice.
When the option is off and you can visit the 2 different header files in
separate buffers, what does `C-h v buffer-file-truename' say in each
buffer?
--
Kevin Rodgers
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-12-22 17:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-22 11:51 Bug with find-file-existing-other-name option Richard Skinner
[not found] <mailman.8081.1103717102.27204.bug-gnu-emacs@gnu.org>
2004-12-22 17:54 ` Kevin Rodgers
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).