From: Michael Albinus <michael.albinus@gmx.de>
To: Juri Linkov <juri@linkov.net>
Cc: 50976@debbugs.gnu.org
Subject: bug#50976: 28.0.50; Tramp read-file-name regression
Date: Tue, 05 Oct 2021 16:32:34 +0200 [thread overview]
Message-ID: <8735pf5ypp.fsf@gmx.de> (raw)
In-Reply-To: <8735plort6.fsf@mail.linkov.net> (Juri Linkov's message of "Sat, 02 Oct 2021 22:19:25 +0300")
Juri Linkov <juri@linkov.net> writes:
Hi Juri,
> This is a recent regression. When visiting a remote Dired buffer,
> marking one file with C-SPC (set-mark-command), then moving point
> to another Dired file, then typing '=' (dired-diff) and 'RET'
> fails with the error "Attempt to compare the file to itself".
>
> This is because 'read-file-name' in the interactive spec of 'dired-diff'
> now returns the remote directory name after typing RET,
> while some time ago it correctly returned the default file name,
> that is the marked file that was used as the arg 'file' of 'dired-diff'.
>
> In local filesystems, RET still correctly returns the default file,
> not a directory name as it does now for remote directories.
FTR, git bisect has identified the following guilty commit:
--8<---------------cut here---------------start------------->8---
commit 225ca617b70d3c70376c2d9bf38ced2f2323b26e (refs/bisect/bad)
Author: Michael Albinus <michael.albinus@gmx.de>
Date: Fri Jul 2 14:51:23 2021 +0200
Implement another fix for bug#49229
* lisp/minibuffer.el (read-file-name-default): Respect remote files.
(Bug#49229)
--8<---------------cut here---------------end--------------->8---
I will check how bug#49229 could be fixed differently.
Best regards, Michael.
next prev parent reply other threads:[~2021-10-05 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 19:19 bug#50976: 28.0.50; Tramp read-file-name regression Juri Linkov
2021-10-05 14:32 ` Michael Albinus [this message]
2021-10-08 14:36 ` Michael Albinus
2021-10-23 13:29 ` Michael Albinus
2021-10-23 18:09 ` Juri Linkov
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=8735pf5ypp.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=50976@debbugs.gnu.org \
--cc=juri@linkov.net \
/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.