unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Pascal Quesseveur <pquessev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Change in 28.1 in opening a file from grep results on Windows
Date: Tue, 12 Jul 2022 18:56:59 +0200	[thread overview]
Message-ID: <82czea8e1w.fsf@gmail.com> (raw)
In-Reply-To: 83tu7mwbav.fsf@gnu.org

>"EZ" == Eli Zaretskii <eliz@gnu.org> writes:

  EZ> The reason for the change is described in bug#8035, which is even
  EZ> nastier than this one.  So we cannot possibly go back to the old code
  EZ> there.

Ok.

  EZ> It is IME unusual to use literal UNCs in serious development on
  EZ> MS-Windows, precisely because cmd.exe doesn't support that well, and
  EZ> various commands will fail depending on how you invoke them and what
  EZ> is the working directory when you do.  Wherever I saw networked drive
  EZ> used it was always via mapping them to a drive letter, and for a good
  EZ> reason.

  EZ> So I still think this is the right solution, not even a workaround,
  EZ> because the same problems will happen outside Emacs if you use cmd.exe
  EZ> as your shell.

When I use cmd, I follow the symbolic link and I don't get problems. I
use some IDEs which work fine also, the only problem is that regularly
they save the absolute path in the config files, but I can manage
that.

It's still not very consistent in Emacs. If I open a dired buffer on
the linked directory, and open a file from the dired buffer, its path
is that of the linked directory. If I open a file from the compilation
buffer its path is that of the target directory.


-- 
Pascal Quesseveur
pquessev@gmail.com




  reply	other threads:[~2022-07-12 16:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 15:36 Change in 28.1 in opening a file from grep results on Windows Pascal Quesseveur
2022-07-12 16:01 ` Eli Zaretskii
2022-07-12 16:31   ` Pascal Quesseveur
2022-07-12 16:50     ` Eli Zaretskii
2022-07-12 17:04       ` Pascal Quesseveur
2022-07-12 17:13         ` Eli Zaretskii
2022-07-12 17:23           ` Pascal Quesseveur
2022-07-12 16:22 ` Eli Zaretskii
2022-07-12 16:56   ` Pascal Quesseveur [this message]
2022-07-12 17:09     ` Eli Zaretskii
2022-07-12 17:20       ` Pascal Quesseveur
2022-07-12 17:29         ` Eli Zaretskii
2022-07-12 17:41           ` Pascal Quesseveur
2022-07-12 20:07     ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-13 12:14       ` Eli Zaretskii
2022-07-13 12:47         ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-13 16:08           ` Pascal Quesseveur

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=82czea8e1w.fsf@gmail.com \
    --to=pquessev@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).