From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
To: 29972@debbugs.gnu.org
Subject: bug#29972: 25.3; dired-hide-details-mode does not persist in desktop session
Date: Mon, 8 Jan 2018 12:43:38 +0000 [thread overview]
Message-ID: <CAKDRQS5J4AtHqc7kSVasNa8ji_tP8LGSwRRDdiHzgxP6AUYq2Q@mail.gmail.com> (raw)
In-Reply-To: <CAM-tV-8=B0-X_QEMizvoevXmpYb5O3TwQp3+j41RrFkYoVjWmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
Does that mean this patch can't be merged until we've figured a way out by
changing `define-minor-mode` to introduce a new `buffer-minor-modes` buffer
local variable?
On Fri, Jan 5, 2018 at 7:59 PM, Noam Postavsky <
npostavs@users.sourceforge.net> wrote:
> On Fri, Jan 5, 2018 at 2:56 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> >> (I see describe-mode only takes minor modes which have function and
> >> variable using the same symbol)
> >
> > That happens automagically if one uses define-minor-mode, right?
>
> Except if you use its :variable option.
>
[-- Attachment #2: Type: text/html, Size: 974 bytes --]
next prev parent reply other threads:[~2018-01-08 12:43 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 [this message]
2018-01-08 18:54 ` Eli Zaretskii
[not found] ` <<83r2r06v1y.fsf@gnu.org>
2018-01-08 19:08 ` Drew Adams
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=CAKDRQS5J4AtHqc7kSVasNa8ji_tP8LGSwRRDdiHzgxP6AUYq2Q@mail.gmail.com \
--to=wyuenho@gmail.com \
--cc=29972@debbugs.gnu.org \
/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).