From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: psainty@orcon.net.nz, 38111@debbugs.gnu.org
Subject: bug#38111: 27.0.50; globalized-minor-mode not enabled on get-buffer-create
Date: Sun, 20 Sep 2020 13:06:27 +0200 [thread overview]
Message-ID: <87zh5koggc.fsf@gnus.org> (raw)
In-Reply-To: <87k176xxjh.fsf@mail.linkov.net> (Juri Linkov's message of "Mon, 09 Dec 2019 00:27:52 +0200")
Juri Linkov <juri@linkov.net> writes:
>>> The following patch fixes this, but I'm still not sure if we need
>>> to grep all occurrences of get-buffer-create and add set-buffer-major-mode
>>> everywhere?
>>
>> This is a problem with all globalized minor modes, right?
>
> Yes, with all globalized minor modes.
>
> So I installed the patch that fixes this particular case,
> and leaving this bug report open waiting for a more general solution.
I don't think a general solution is really possible here. We don't want
any get-buffer-create to run the globalised modes -- that would be slow
and awkward. We only want those to run in buffers that users actually
end up using, and I think that's something the modes themselves must
somehow decide.
So I don't think there's any realistic progress to be made in this bug
report, and I'm closing it.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2020-09-20 11:06 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
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 [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=87zh5koggc.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=38111@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=psainty@orcon.net.nz \
/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).