unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 38111@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#38111: 27.0.50; globalized-minor-mode not enabled on get-buffer-create
Date: Wed, 13 Nov 2019 11:42:07 +1300	[thread overview]
Message-ID: <b7a4b75aa812be3d838ca95975686a61@webmail.orcon.net.nz> (raw)
In-Reply-To: <83y2wqd7ec.fsf@gnu.org>

On 2019-11-08 22:50, Eli Zaretskii wrote:
> Sounds like globalized-minor-mode machinery somehow doesn't support
> the latter method of creating a buffer?

Yep, globalized modes use `after-change-major-mode-hook' to call the
buffer-local minor mode, and that hook is not triggered in these cases
because, although new buffers are in `fundamental-mode' by default,
the `fundamental-mode' function is not actually called, and so no mode
change occurs.

I believe this has cropped up in past discussion, but I don't recall
where offhand.

I agree that it's surprising when you are expecting the global mode(s)
to be enabled (I first realised it when attempting to use a globalized
mode for my custom key bindings, and discovering they were not being
enabled in various buffers).

If this were changed then there *might* be undesirable consequences to
having lots of created-behind-the-scenes buffers suddenly doing things
they never did before.

If the current behaviour is kept, the documentation for globalized
modes and for creating buffers should probably say something about the
matter.


-Phil






  parent reply	other threads:[~2019-11-12 22:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 21:53 bug#38111: 27.0.50; globalized-minor-mode not enabled on get-buffer-create Juri Linkov
2019-11-08  9:50 ` Eli Zaretskii
2019-11-12 20:33   ` Juri Linkov
2019-11-12 22:42   ` Phil Sainty [this message]
2019-11-13 21:12     ` Juri Linkov
2019-11-15  9:02     ` Eli Zaretskii
2019-12-07 22:56     ` Juri Linkov
2019-12-08 16:54       ` Eli Zaretskii
2019-12-08 22:27         ` Juri Linkov
2020-09-20 11:06           ` Lars Ingebrigtsen

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=b7a4b75aa812be3d838ca95975686a61@webmail.orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=38111@debbugs.gnu.org \
    --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).