GNU bug report logs -
#64131
make resolving symlinks in compilation-find-file optional
Previous Next
Reported by: Qiang Fang <qiang.fang <at> zoho.com.cn>
Date: Sat, 17 Jun 2023 14:28:02 UTC
Severity: normal
Tags: moreinfo
Done: Stefan Kangas <stefankangas <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Qiang <qiang.fang <at> zoho.com.cn> writes:
> 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.
Could you provide a recipe for how to test this, for someone that
doesn't use git-annex but would be happy to install it?
Or even better, could you produce a recipe that doesn't rely on
git-annex?
This bug report was last modified 349 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.