From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: 74700@debbugs.gnu.org
Subject: bug#74700: [PATCH] Revert Dired buffer when clicking on last segment of directory name
Date: Thu, 05 Dec 2024 09:02:01 +0200 [thread overview]
Message-ID: <86ttbiy5na.fsf@gnu.org> (raw)
In-Reply-To: <874j3iodzb.fsf@gmail.com> (message from Visuwesh on Thu, 05 Dec 2024 11:42:08 +0530)
> From: Visuwesh <visuweshm@gmail.com>
> Date: Thu, 05 Dec 2024 11:42:08 +0530
>
> Attached patch makes it possible to revert the current Dired buffer by
> clicking on the last segment of the directory line. With the patch
> applied,
>
> /home/viz/lib/ports/emacs:
>
> clicking on 'emacs' now reverts the buffer that shows ~/lib/ports/emacs.
> Previously, it did nothing. This makes it possible to update the Dired
> listing without needing to use the keyboard.
Thanks, a few comments below.
> +---
> +*** Clicking on last segment of directory reverts buffer
> +When 'dired-make-directory-clickable' is non-nil, clicking on the last
> +segment of the directory name now reverts the Dired buffer.
We don't call these "segments", we call them "components". And since
you are talking about the last one, you could also say "base name of
the directory".
> + (when (search-forward ":" bound t)
> + (add-text-properties
> + segment-start (1- (point))
> + `( mouse-face highlight
^^
We don't leave whitespace after the opening parenthesis.
> + help-echo "mouse-1: revert this buffer"
I think the help-echo should say something more similar to what we say
for the other components of the directory shown in the header line.
Something like "re-read this buffer's directory".
> + keymap ,(define-keymap
> + "<mouse-2>" #'revert-buffer
> + "<follow-link>" 'follow-link
> + "RET" #'revert-buffer))))))))
Should we perhaps call dired-revert directly?
next prev parent reply other threads:[~2024-12-05 7:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 6:12 bug#74700: [PATCH] Revert Dired buffer when clicking on last segment of directory name Visuwesh
2024-12-05 7:02 ` Eli Zaretskii [this message]
2024-12-05 8:26 ` Visuwesh
2024-12-05 8:41 ` Eli Zaretskii
2024-12-05 9:02 ` Visuwesh
2024-12-05 9:24 ` Eli Zaretskii
2024-12-05 10:42 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-05 17:56 ` 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
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=86ttbiy5na.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74700@debbugs.gnu.org \
--cc=visuweshm@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).