From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 45127@debbugs.gnu.org
Subject: bug#45127: 28.0.50; wdired + dired-hide-details-mode toggling?
Date: Fri, 28 Jan 2022 15:56:39 +0100 [thread overview]
Message-ID: <875yq3hpso.fsf@gnus.org> (raw)
In-Reply-To: <87blf4f0dj.fsf@web.de> (Michael Heerdegen's message of "Tue, 08 Dec 2020 22:34:16 +0100")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> My wishlist proposal is: may we allow to toggle
> `dired-hide-details-mode' in a wdired buffer (currently an error is
> signaled in this case)? I ask because (1) seems this would work out of
> the box, and (2) it may be useful, e.g. because I started with hidden
> details, already have performed some changes, and see that I need to
> change something in the details also. Or I have long filenames and thus
> want to hide details although I have already switched to wdired.
>
> Anyway, the implementation of d-h-details-mode only seems to toggle some
> invisibility spec, and thus I expect no problems (will try it out
> privately in the meantime).
>
> I guess we would need a new key for it, since the binding for toggling,
> "(", is bound to self-insert-command in a wdired buffer. C-c ( maybe?
I tried it out for a bit, and it seems to work without any problems, so
I lifted the dired-mode restriction and added the key binding in Emacs 29.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-01-28 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 21:34 bug#45127: 28.0.50; wdired + dired-hide-details-mode toggling? Michael Heerdegen
2020-12-08 22:18 ` Drew Adams
2020-12-08 22:28 ` Michael Heerdegen
2020-12-08 22:45 ` Drew Adams
2020-12-08 22:47 ` Michael Heerdegen
2020-12-08 22:57 ` Drew Adams
2020-12-08 23:49 ` Michael Heerdegen
2020-12-09 0:15 ` Drew Adams
2022-01-28 14:56 ` Lars Ingebrigtsen [this message]
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=875yq3hpso.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=45127@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).