From: Richard Skinner <richard.skinner@myrealbox.com>
Subject: [Fwd: Bug with find-file-existing-other-name option]
Date: Wed, 22 Dec 2004 11:55:32 +0000 [thread overview]
Message-ID: <1103716532.8893.16.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 79 bytes --]
Apologies - didn't include the version info in original mail. GNU Emacs
21.3.1
[-- Attachment #2: Forwarded message - Bug with find-file-existing-other-name option --]
[-- Type: message/rfc822, Size: 1137 bytes --]
From: Richard Skinner <richard.skinner@myrealbox.com>
To: bug-gnu-emacs@gnu.org
Subject: Bug with find-file-existing-other-name option
Date: Wed, 22 Dec 2004 11:51:00 +0000
Message-ID: <1103716260.8893.14.camel@localhost>
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.
[-- Attachment #3: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Bug-gnu-emacs mailing list
Bug-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs
reply other threads:[~2004-12-22 11:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1103716532.8893.16.camel@localhost \
--to=richard.skinner@myrealbox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).