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>
Cc: "52007@debbugs.gnu.org" <52007@debbugs.gnu.org>
Subject: bug#52007: [External] : Re: bug#52007: 26.3; Doc of `define-globalized-minor-mode' and global(ized) minor modes
Date: Sun, 21 Nov 2021 17:22:30 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488DF469AA877EA7DA0C723F39E9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83bl2erow3.fsf@gnu.org>

> > It's even worse than I thought.
> >
> > The first line of the doc string of the globalized
> > version of minor mode `foo-mode' (`global-foo-mode')
> > says that it toggles `foo-mode' everywhere:
> >
> >   Toggle Foo mode in all buffers.
> >
> > It doesn't do that at all.  Instead, it toggles
> > `global-foo-mode'.
> 
> No, it turns ON both foo-mode and global-foo-mode.

You missed the point of the bug report.
Toggling the global mode turns them both on (or off,
depending on the current value of `global-foo-mode')
in all buffers, yes.

That's not what it means to toggle `foo-mode'
everywhere.  Doing that would flip the value that
`foo-mode' (non-global mode) has in each buffer.

Correcting the doc to say that it toggles the
global mode was correct.  Saying that it toggles
the local mode everywhere was incorrect.

Glad this will be fixed in Emacs 28.  (And no, I
wasn't "looking at an old Emacs".  I reported on
the latest Emacs release, Emacs 27.2.)





  reply	other threads:[~2021-11-21 17:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-20 22:44 bug#52007: 26.3; Doc of `define-globalized-minor-mode' and global(ized) minor modes Drew Adams
2021-11-20 23:17 ` Drew Adams
2021-11-21  6:42   ` Eli Zaretskii
2021-11-21 17:22     ` Drew Adams [this message]
2021-11-21 17:28       ` bug#52007: [External] : " Eli Zaretskii
2021-11-21 17:45         ` Drew Adams
2021-11-21 18:03           ` Eli Zaretskii
2021-11-21 18:25             ` Drew Adams
2021-11-21  6:41 ` Eli Zaretskii

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=SJ0PR10MB5488DF469AA877EA7DA0C723F39E9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=52007@debbugs.gnu.org \
    --cc=eliz@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).