From: Dmitry Gutov <dgutov@yandex.ru>
To: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>,
61449@debbugs.gnu.org
Subject: bug#61449: 30.0.50; diff-hl-dired: Consider adding a cookie to diff-hl-dired overlay
Date: Sun, 12 Feb 2023 15:12:27 +0200 [thread overview]
Message-ID: <76d0d86a-8e43-6534-0ad0-016ef1fe62c8@yandex.ru> (raw)
In-Reply-To: <TY2PR0101MB3693A169203A1DD38A8F4C6CDADC9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com>
On 12/02/2023 07:32, Ramesh Nedunchezian wrote:
> 1. `diff-hl-dired-mode` kicks of an async process, and I wanted some
> visual indication that the async process has finished, and I am
> seeing ALL OF the unknown files. I would have appreciated an echo
> area message, or a mode line indicator that the process has
> finished.
I was worried it could be too distracting, to show that every time one
enters a directory. Perhaps a user option could be added.
> 2. `C-x v d` recursively lists all "unregistered" files, but
> `diff-hl-dired-mode` lists only the entries in current directory.
>
> I would have appreciated an option to do a recursive listing of
> files ....
I'm pretty sure the unregistered files are mentioned recursively. But
the indicator is put on the containing directory. How else would we do that?
next prev parent reply other threads:[~2023-02-12 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 5:32 bug#61449: 30.0.50; diff-hl-dired: Consider adding a cookie to diff-hl-dired overlay Ramesh Nedunchezian
[not found] ` <handler.61449.B.167618026110384.ack@debbugs.gnu.org>
2023-02-12 5:41 ` bug#61449: Acknowledgement (30.0.50; diff-hl-dired: Consider adding a cookie to diff-hl-dired overlay) Ramesh Nedunchezian
2023-02-12 6:34 ` bug#61449: 30.0.50; diff-hl-dired: Consider adding a cookie to diff-hl-dired overlay Ramesh Nedunchezian
2023-02-12 13:12 ` Dmitry Gutov [this message]
2023-02-13 11:32 ` Ramesh Nedunchezian
2023-02-12 13:12 ` Dmitry Gutov
2023-02-13 11:19 ` Ramesh Nedunchezian
2023-02-18 23:25 ` Dmitry Gutov
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=76d0d86a-8e43-6534-0ad0-016ef1fe62c8@yandex.ru \
--to=dgutov@yandex.ru \
--cc=61449@debbugs.gnu.org \
--cc=rameshnedunchezian@outlook.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).