From: Qiang via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Qiang <qiang.fang@zoho.com.cn>, 64131@debbugs.gnu.org
Subject: bug#64131: make resolving symlinks in compilation-find-file optional
Date: Tue, 12 Sep 2023 09:01:09 +0800 [thread overview]
Message-ID: <87cyyob3xm.wl-qiang.fang@zoho.com.cn> (raw)
In-Reply-To: <CADwFkmka7yOstSCtAcryDgMDSfDJO2GiWsN=z4W9xyMLivag5g@mail.gmail.com>
Without that tiny modification, I have problem jump to the file in my git-annex folder, it jump to the actual database folder, what I want to the folder that have the symlink. I think it should be the default.
People use symlinks to organize text documents, a file may have links in different dirs. For example, if we use dirs as catalogues, when a file is opened following the search result in a "rg" buffer, it would be convenient to jump to the catalogue by just M-x "dired". However, the current behavior is to jump to the dir that has the symlink destination file. For people using git-annex, the symlink destination dir could be a database dir, and it is not supposed to be accessed directly.
next prev parent reply other threads:[~2023-09-12 1:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 13:18 bug#64131: make resolving symlinks in compilation-find-file optional Qiang Fang via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 18:06 ` Stefan Kangas
2023-09-11 23:56 ` Qiang via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 0:33 ` Stefan Kangas
2023-09-12 0:59 ` Qiang via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 1:01 ` Qiang via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-01-10 10:39 ` Stefan Kangas
2024-01-10 13:29 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cyyob3xm.wl-qiang.fang@zoho.com.cn \
--to=bug-gnu-emacs@gnu.org \
--cc=64131@debbugs.gnu.org \
--cc=qiang.fang@zoho.com.cn \
--cc=stefankangas@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.