From: Tino Calancha <tino.calancha@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, stefan@marxist.se, jidanni@jidanni.org,
39145@debbugs.gnu.org, larsi@gnus.org, uyennhi.qm@gmail.com
Subject: bug#39145: 28.0.50; dired: Show broken/circular links in different font
Date: Tue, 25 Aug 2020 19:18:06 +0200 [thread overview]
Message-ID: <87y2m2r6ep.fsf@gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.22.394.2008251900570.19452@localhost.example.com> (Tino Calancha's message of "Tue, 25 Aug 2020 19:05:11 +0200 (CEST)")
Tino Calancha <tino.calancha@gmail.com> writes:
> On Tue, 25 Aug 2020, Eli Zaretskii wrote:
>
>> Even if you have auto-revert-mode turned on in that Dired buffer?
> I have tried now with:
>
> dired-auto-revert-mode equals t
> dired-auto-rever-mode equals 'dired-directory-changed-p
>
> I still need to push `g' key to get the link face updated.
Sorry, I tried `dired-auto-revert-mode' not what you said.
You are right, w/ auto-revert-mode ON it matches my expectations: the
link face is updated after changes in the link target.
I am still wondering if the feature should update the face also when
auto-rever-mode is OFF. I like the behavior that I observe with wdired:
If I change the link target with wdired, then the face is updated.
Nice. Wish the same with other dired commands changing the link target.
next prev parent reply other threads:[~2020-08-25 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 21:06 bug#39145: 28.0.50; dired: Show broken/circular links in different font Tino Calancha
2020-01-15 22:28 ` Glenn Morris
2020-08-24 18:05 ` Tino Calancha
2020-08-25 16:34 ` Tino Calancha
2020-08-25 16:51 ` Eli Zaretskii
2020-08-25 17:05 ` Tino Calancha
2020-08-25 17:18 ` Tino Calancha [this message]
2020-08-25 18:22 ` Eli Zaretskii
2020-08-27 8:30 ` Tino Calancha
2020-08-27 9:03 ` Eli Zaretskii
2020-08-27 9:37 ` Stefan Kangas
2020-08-27 9:58 ` Tino Calancha
2020-01-15 23:13 ` Juri Linkov
2020-08-24 17:52 ` Tino Calancha
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=87y2m2r6ep.fsf@gmail.com \
--to=tino.calancha@gmail.com \
--cc=39145@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
--cc=rgm@gnu.org \
--cc=stefan@marxist.se \
--cc=uyennhi.qm@gmail.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).