From: spucci <slpnabble@blackberry-hill.com>
To: 8035@debbugs.gnu.org
Subject: bug#8035: Processing of .. in a file path after going thru symlink
Date: Sun, 13 Feb 2011 19:05:40 -0800 (PST) [thread overview]
Message-ID: <30918394.post@talk.nabble.com> (raw)
The behavior is general, but it's a particular problem with next-error:
When emacs attempts to find a file with "../" as a path component, it
appears to be "smart" about it and simply remove the previous directory path
(e.g., "foo/bar/../x" gets converted to "foo/x"). But if bar is a symlink,
then it doesn't properly find the file. So in compiler output, which
references such files, the next-error function fails to find the file with
the given name.
mkdir dest
mkdir dest/subdir
mkdir src
ln -s ../dest/subdir src/subdir
echo "#error This is an error" > dest/foo.c
Now M-x compile, and give it cc -c src/subdir/../foo.c
*compilation* buffer has:
cc -c src/subdir/../foo.c
src/subdir/../foo.c:1:2: error: #error This is an error
and do a next-error: Emacs complains it can't find the file. And if you try
to find-file that file path (src/subdir/../foo.c) it doesn't work either.
Nor does "emacsclient src/subdir/../foo.c. I couldn't find an option to
disable this behavior; it seems like there should be one even if the default
continues to be as it is today.
This is Gnu Emacs 23.2.1 I built myself on MacOS X 10.6.6.
Thanks,
Steve
--
View this message in context: http://old.nabble.com/Processing-of-..-in-a-file-path-after-going-thru-symlink-tp30918394p30918394.html
Sent from the Emacs - Bugs mailing list archive at Nabble.com.
next reply other threads:[~2011-02-14 3:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 3:05 spucci [this message]
2011-02-19 21:37 ` bug#8035: Processing of .. in a file path after going thru symlink Glenn Morris
2011-02-20 2:35 ` Steve Pucci
2011-02-20 2:41 ` Steve Pucci
2021-08-26 16:29 ` Lars Ingebrigtsen
2021-08-26 16:44 ` Eli Zaretskii
2021-08-26 17:03 ` Lars Ingebrigtsen
2021-08-26 17:08 ` Eli Zaretskii
2021-08-26 17:24 ` Lars Ingebrigtsen
2021-08-26 17:30 ` Eli Zaretskii
2021-08-26 16:53 ` Andreas Schwab
2021-08-26 17:04 ` Lars Ingebrigtsen
2021-08-26 17:19 ` Andreas Schwab
2021-08-26 17:30 ` Lars Ingebrigtsen
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=30918394.post@talk.nabble.com \
--to=slpnabble@blackberry-hill.com \
--cc=8035@debbugs.gnu.org \
/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).