From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Jimmy Yuen Ho Wong <wyuenho@gmail.com>
Cc: 29972@debbugs.gnu.org
Subject: bug#29972: 25.3; dired-hide-details-mode does not persist in desktop session
Date: Mon, 8 Jan 2018 11:08:24 -0800 (PST) [thread overview]
Message-ID: <f8d1aa8b-e7a1-4f49-a888-1e4fc16936d7@default> (raw)
In-Reply-To: <<83r2r06v1y.fsf@gnu.org>>
> We need to figure out some way for desktop.el to record
> dired-hide-details-mode, either automatically or given user
> customizations.
>
> It's possible that looking at minor-mode-list (not minor-mode-alist!)
> is such a way.
Yes, that's no doubt possible. Perhaps it's also possible
to make changes to variable `dired-hide-details-mode' change
the mode. If so then you could just add that variable to
the default value of `desktop-locals-to-save'. And since
that's a user option, users could then control whether that's
the behavior they want, i.e., whether desktop should restore
whether details were shown/hidden.
next prev parent reply other threads:[~2018-01-08 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 1:11 bug#29972: 25.3; dired-hide-details-mode does not persist in desktop session Yuen Ho Wong
2018-01-04 16:42 ` Eli Zaretskii
2018-01-05 13:08 ` Jimmy Yuen Ho Wong
2018-01-05 14:25 ` Eli Zaretskii
2018-01-05 15:02 ` Jimmy Yuen Ho Wong
2018-01-05 15:16 ` Eli Zaretskii
2018-01-05 17:42 ` Jimmy Yuen Ho Wong
2018-01-05 18:20 ` Eli Zaretskii
2018-01-05 18:29 ` Noam Postavsky
2018-01-05 18:37 ` Drew Adams
2018-01-05 19:41 ` Eli Zaretskii
2018-01-05 19:54 ` Noam Postavsky
2018-01-05 19:56 ` Eli Zaretskii
2018-01-05 19:59 ` Noam Postavsky
2018-01-08 12:43 ` Jimmy Yuen Ho Wong
2018-01-08 18:54 ` Eli Zaretskii
[not found] ` <<83r2r06v1y.fsf@gnu.org>
2018-01-08 19:08 ` Drew Adams [this message]
2022-04-17 18:22 ` Lars Ingebrigtsen
[not found] <<m28tdezavi.fsf@mobilecat.lan>
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=f8d1aa8b-e7a1-4f49-a888-1e4fc16936d7@default \
--to=drew.adams@oracle.com \
--cc=29972@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=wyuenho@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).