From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Drew Adams <drew.adams@oracle.com>
Cc: 14940@debbugs.gnu.org
Subject: bug#14940: 24.3.50; [PATCH] enhancement for `dired-hide-details-mode'
Date: Thu, 25 Jul 2013 14:30:00 -0400 [thread overview]
Message-ID: <jwvr4emo64f.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <42783abc-5cff-41d5-8b9d-e7e641584cb6@default> (Drew Adams's message of "Tue, 23 Jul 2013 09:28:59 -0700 (PDT)")
> 1. Users can decide whether the initial hide/show state of new Dired
> buffers reflects the last chosen state for a Dired buffer. This is
> decided by option `dired-hide-details-propagate'. Non-nil means
> propagate the last chosen state as the initial state of a new Dired
> buffer.
> 2. If `dired-hide-details-propagate' is nil, or if the user has not
> yet explicitly changed any Dired hide/show state, then option
> `dired-hide-details-initially' defines the initial state of a new
> Dired buffer. IOW, it specifies what the "last" state defaults to.
Hmm... couldn't we merge those two configuration variables?
Here's the idea:
- Rename dired-hide-details-initially to dired-hide-details-default-mode,
a new (global) minor mode which determines how new dired buffers show up.
- Make it so that toggling dired-hide-details-default-mode also toggles the
dired-hide-details-mode in the current buffer.
This way, instead of setting dired-hide-details-propagate to t, users
can simply use dired-hide-details-default-mode instead of
dired-hide-details-mode.
Stefan
PS: Your code often exceeds the 80 columns limit.
next prev parent reply other threads:[~2013-07-25 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 16:28 bug#14940: 24.3.50; [PATCH] enhancement for `dired-hide-details-mode' Drew Adams
2013-07-25 18:30 ` Stefan Monnier [this message]
2013-07-26 0:57 ` Drew Adams
2013-11-04 16:31 ` Stefan Monnier
2013-11-04 16:34 ` Jambunathan K
2013-11-04 17:35 ` Drew Adams
2013-11-04 15:33 ` Jambunathan K
2019-06-26 15:34 ` Lars Ingebrigtsen
2019-06-26 15:42 ` Drew Adams
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=jwvr4emo64f.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=14940@debbugs.gnu.org \
--cc=drew.adams@oracle.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).