From: Drew Adams <drew.adams@oracle.com>
To: Tomas Nordin <tomasn@posteo.net>, help-gnu-emacs@gnu.org
Subject: RE: dired-hide-details-mode have no effect suddenly
Date: Sun, 3 Sep 2017 11:04:28 -0700 (PDT) [thread overview]
Message-ID: <e8d996ed-28f0-474e-8fa1-02b2c53ed1e4@default> (raw)
In-Reply-To: <87d1774qr8.fsf@fliptop>
> Here is a problem I don't know how to reproduce. I have this in my
> .emacs:
>
> (add-hook 'dired-mode-hook 'dired-hide-details-mode)
>
> and details are hidden by default, the way I like it. Sometimes I need
> to see some details and I use (default I think) the key ( to toggle
> visibility of details.
>
> However, suddenly after some long time of keeping emacs alive, details
> are always shown and I cannot toggle it. I have been trying to detect at
> what moment this happens but I fail to understand what the interference
> is. At this point all I can think of is restarting emacs. Did somebody
> notice a similar problem?
Do you see the same thing if you start Emacs using `emacs -Q'
(no init file)? If so, it sounds like a bug
(`M-x report-emacs-bug').
Do you perhaps use library `dired-details+.el'? If so, and if
option `dired-details-propagate-flag' has its default value
of `t', and if you happen to use `(` in Dired (to toggle
showing details), then that the resulting state is used from
then on (until you hit `(` again), by default.
IOW, that could explain what you think you see. If you did
hit `(` then what you get from that (e.g. showing details)
will be what you see in Dired from then on (until you toggle
with `(` again). If you don't want such propagation then
customize the option value to `nil'.
https://www.emacswiki.org/emacs/download/dired-details%2b.el
next prev parent reply other threads:[~2017-09-03 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 17:48 dired-hide-details-mode have no effect suddenly Tomas Nordin
2017-09-03 18:04 ` Drew Adams [this message]
2017-09-03 18:52 ` Tomas Nordin
2017-09-03 19:37 ` Drew Adams
2017-09-09 19:34 ` Tomas Nordin
2017-09-09 22:48 ` Drew Adams
2017-09-12 20:40 ` Tomas Nordin
2017-09-05 19:10 ` Charles A. Roelli
2017-09-09 19:25 ` Tomas Nordin
2017-09-20 20:49 ` Tomas Nordin
2017-09-21 18:30 ` Charles A. Roelli
2017-09-21 19:10 ` Tomas Nordin
2017-09-21 19:20 ` Tomas Nordin
2017-09-23 9:43 ` Charles A. Roelli
2017-09-24 15:49 ` Tomas Nordin
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=e8d996ed-28f0-474e-8fa1-02b2c53ed1e4@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tomasn@posteo.net \
/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.
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).