unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Anders Gustavsson <anders_r_gson@yahoo.com>
Cc: 75363@debbugs.gnu.org
Subject: bug#75363: 29.3; compile-goto-error eliminates symbolic links
Date: Sat, 04 Jan 2025 21:03:19 +0200	[thread overview]
Message-ID: <86jzbabdvs.fsf@gnu.org> (raw)
In-Reply-To: <961853769.14912292.1736004372047@mail.yahoo.com> (bug-gnu-emacs@gnu.org)

> Date: Sat, 4 Jan 2025 15:26:12 +0000 (UTC)
> From:  Anders Gustavsson via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Create a directory, a file and a shortcut in the file system:
> 
> cd
> mkdir -p path/to/long/directory/in/file/system
> echo "hello" > path/to/long/directory/in/file/system/file
> ln -s path/to/long/directory/in/file/system/ shortcut
> 
> In emacs
> 
> C-x C-f shortcut
> M-x grep <ret> hello * <ret>
> 
> in the output mouse-1 on
> 
> file 1:hello
> 
> Then type: C-x C-b
> 
> Then you see that the filename of the file found in the grep output is 
> ~/path/to/long/directory/in/file/system/file
> 
> not ~/shortcut/file as you would have expected, and how it was before in
> emacs version 27.1. Same thing happens in emacs 29.4.

I think this is already fixed in Emacs 30, where it only resolves
symlinks if the shortcut name cannot be found by find-file.

Can you try the latest pretest of Emacs 30.1?  Its tarball is here:

  https://alpha.gnu.org/gnu/emacs/pretest/emacs-30.0.93.tar.xz





  reply	other threads:[~2025-01-04 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <961853769.14912292.1736004372047.ref@mail.yahoo.com>
2025-01-04 15:26 ` bug#75363: 29.3; compile-goto-error eliminates symbolic links Anders Gustavsson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-04 19:03   ` Eli Zaretskii [this message]
2025-01-05  6:24   ` bug#75363: already fixed Anders Gustavsson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-05  9:16     ` 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=86jzbabdvs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=75363@debbugs.gnu.org \
    --cc=anders_r_gson@yahoo.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).