unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
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:51:59 +0300	[thread overview]
Message-ID: <83o8my4qj4.fsf@gnu.org> (raw)
In-Reply-To: <871rjusn0f.fsf@gmail.com> (message from Tino Calancha on Tue, 25 Aug 2020 18:34:08 +0200)

> From: Tino Calancha <tino.calancha@gmail.com>
> Cc: uyennhi.qm@gmail.com,  rgm@gnu.org, eliz@gnu.org, jidanni@jidanni.org,
>  larsi@gnus.org, stefan@marxist.se
> Date: Tue, 25 Aug 2020 18:34:08 +0200
> 
> There is still something else that worries me.
> 
> If I have a broken link, and I create the missing target with
> `dired-create-directory' or `dired-create-empty-file', then
> I need to manually call `revert-buffer' to get the link face updated.
> 
> Same if teh target do exist and I decide to delete it with
> `dired-do-delete'.

Even if you have auto-revert-mode turned on in that Dired buffer?





  reply	other threads:[~2020-08-25 16:51 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 [this message]
2020-08-25 17:05         ` Tino Calancha
2020-08-25 17:18           ` Tino Calancha
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=83o8my4qj4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39145@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@gnus.org \
    --cc=rgm@gnu.org \
    --cc=stefan@marxist.se \
    --cc=tino.calancha@gmail.com \
    --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).