From: Stephen Berman <Stephen.Berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61510@debbugs.gnu.org, Stephen Berman <stephen.berman@gmx.net>,
cornejodlm@ciencias.unam.mx
Subject: bug#61510: Aw: Re: bug#61510: 28.2; dired-hide-details-mode shows symlink targets after entering and exiting wdired
Date: Sun, 19 Feb 2023 11:48:58 +0100 [thread overview]
Message-ID: <trinity-d4e7ac3a-6efe-44c7-bcd2-1ad63669f2c5-1676803737864@msvc-mesg-gmx104> (raw)
In-Reply-To: <837cwfylh4.fsf@gnu.org>
> Gesendet: Samstag, den 18.02.2023 um 17:41 Uhr
> Von: "Eli Zaretskii" <eliz@gnu.org>
> An: "Stephen Berman" <stephen.berman@gmx.net>
> Cc: cornejodlm@ciencias.unam.mx, 61510@debbugs.gnu.org
> Betreff: Re: bug#61510: 28.2; dired-hide-details-mode shows symlink targets after entering and exiting wdired
>
> > From: Stephen Berman <stephen.berman@gmx.net>
> > Cc: Iñaki Cornejo de la Mora <cornejodlm@ciencias.unam.mx>,
> > 61510@debbugs.gnu.org
> > Date: Wed, 15 Feb 2023 00:44:55 +0100
> >
> > > To make the investigation of this issue easier, could you please post
> > > a step-by-step recipe for reproducing this starting from "emacs -Q"?
> >
> > I can reproduce the problem:
>
> Thanks.
>
> > With the patch below the result after step 4 is "bla ->". But I haven't
> > tested it with any other case, so maybe it has unwanted consequences.
>
> I think this is the right fix, so please install this on the emacs-29
> branch.
Thanks. I'm traveling right now and won't be able to do that till I return next Friday.
Steve Berman
next prev parent reply other threads:[~2023-02-19 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 16:16 bug#61510: 28.2; dired-hide-details-mode shows symlink targets after entering and exiting wdired Iñaki Cornejo de la Mora
2023-02-14 17:10 ` Eli Zaretskii
2023-02-14 23:44 ` Stephen Berman
2023-02-18 16:41 ` Eli Zaretskii
2023-02-19 10:48 ` Stephen Berman [this message]
2023-02-24 15:48 ` Stephen Berman
2023-02-24 17:03 ` 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=trinity-d4e7ac3a-6efe-44c7-bcd2-1ad63669f2c5-1676803737864@msvc-mesg-gmx104 \
--to=stephen.berman@gmx.net \
--cc=61510@debbugs.gnu.org \
--cc=cornejodlm@ciencias.unam.mx \
--cc=eliz@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.
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).