Re: Bug with find-file-existing-other-name option

[Kevin Rodgers]

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