From: Stefan Kangas <stefankangas@gmail.com>
To: Qiang Fang <qiang.fang@zoho.com.cn>, 64131@debbugs.gnu.org
Subject: bug#64131: make resolving symlinks in compilation-find-file optional
Date: Mon, 11 Sep 2023 11:06:28 -0700 [thread overview]
Message-ID: <CADwFkmnAVQ-weZmjtWdesbPrTKuJoKQLkb1ipE6AUTFB8e8ReQ@mail.gmail.com> (raw)
In-Reply-To: <188c9822598.13072238736789.4931166686046079619@zoho.com.cn>
tags 64131 + moreinfo
thanks
Qiang Fang via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> I use rg for searching in a git-annex repo, rg use compilation-find-file to jump to the file from the search result, symlinks are resolved with file-truename. But it should not resolve the symlink in the above case. See this issue for more details.
>
> https://github.com/dajva/rg.el/issues/156#issuecomment-1595654224
Could you please give a complete recipe to reproduce this, what the
result is and what you expect? Or is this a feature request?
It's preferable if your recipe doesn't include rg.el, because otherwise
it'll be hard for us to test it.
next prev parent reply other threads:[~2023-09-11 18:06 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 [this message]
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
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
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=CADwFkmnAVQ-weZmjtWdesbPrTKuJoKQLkb1ipE6AUTFB8e8ReQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=64131@debbugs.gnu.org \
--cc=qiang.fang@zoho.com.cn \
/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).