From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Emacs Devel <emacs-devel@gnu.org>
Cc: "Duy Nguyễn" <pclouds@gmail.com>
Subject: [BUG] Not following symlinks by default
Date: Sun, 28 Jul 2013 14:44:31 +0530 [thread overview]
Message-ID: <CALkWK0m6=TfcbvDk4_rm_eMeyKkbAHgjHv8JBwqfqT+TVHzJeg@mail.gmail.com> (raw)
Hi,
I've spent many frustrating hours cornering this bug. Here's a short
testcase to reproduce it:
#!/bin/sh
cd /tmp
rm -rf z b
mkdir z z/a z/b
echo ha >z/a/file
ln -s z/b
cd b
cat ../a/file
emacs -Q ../a/file # buffer-file-name = /tmp/a/file
Why doesn't emacs behave like cat or vim? Isn't this behavior a bad default?
Thanks.
next reply other threads:[~2013-07-28 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 9:14 Ramkumar Ramachandra [this message]
2013-07-28 12:02 ` [BUG] Not following symlinks by default Ramkumar Ramachandra
2013-07-28 18:42 ` Glenn Morris
2013-07-28 18:50 ` Ramkumar Ramachandra
2013-07-30 0:42 ` Glenn Morris
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='CALkWK0m6=TfcbvDk4_rm_eMeyKkbAHgjHv8JBwqfqT+TVHzJeg@mail.gmail.com' \
--to=artagnon@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=pclouds@gmail.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).