unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Juri Linkov <juri@linkov.net>
Cc: "dima@secretsauce.net" <dima@secretsauce.net>,
	"57534@debbugs.gnu.org" <57534@debbugs.gnu.org>
Subject: bug#57534: 29.0.50; Highlighting lost after auto-revert-mode triggers
Date: Fri, 2 Sep 2022 14:27:16 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488C2A786446123AED6726EF37A9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <834jxqqlzz.fsf@gnu.org>

> > But this is bug#50431 where 'C-x x g' should be fixed
> > to restore minor modes.
> 
> I'm not sure this is one of the minor modes to be restored.  Maybe
> optionally, but not unconditionally.  See the discussion in that bug.

+2.

Reverting is not about restoring minor modes.
Certainly not blindly so.  Not at all.

Reverting is specific to the major mode.

The major mode gets to decide what reverting
means/does.  The major mode can decide to
restore whatever it likes, including this or
that minor mode.  Nothing should "restore the
minor modes" by default.

My crystal ball whispers that calls for
reverting to "restore minor modes" are trying
to use a sledge hammer where at most a pair
of tweezers might be needed in some uncommon
scenario.





      reply	other threads:[~2022-09-02 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 22:40 bug#57534: 29.0.50; Highlighting lost after auto-revert-mode triggers Dima Kogan
2022-09-02  6:10 ` Eli Zaretskii
2022-09-02  7:04   ` Juri Linkov
2022-09-02  7:22     ` Eli Zaretskii
2022-09-02 14:27       ` Drew Adams [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=SJ0PR10MB5488C2A786446123AED6726EF37A9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=57534@debbugs.gnu.org \
    --cc=dima@secretsauce.net \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.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.
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).