From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 29381@debbugs.gnu.org, Andreas Schwab <schwab@suse.de>,
Paul Rankin <hello@paulwrankin.com>,
Stefan Kangas <stefan@marxist.se>
Subject: bug#29381: show-paren-mode should not be globalized
Date: Fri, 03 Sep 2021 08:58:30 +0200 [thread overview]
Message-ID: <878s0e402x.fsf@gnus.org> (raw)
In-Reply-To: <efdb2f17-37a4-fc22-cace-47a89faef608@orcon.net.nz> (Phil Sainty's message of "Thu, 13 Aug 2020 01:14:12 +1200")
Phil Sainty <psainty@orcon.net.nz> writes:
> Note that show-paren-mode is not "globalized"; it is simply a
> global minor mode. If it was a globalized mode, then there would
> (necessarily) be a buffer-local mode already.
>
> Changing it to a globalized mode would actually be a possible
> solution to your issue, as you could then provide a way for the
> user to determine whether or not the buffer-local mode was enabled
> for any given buffer.
Well... if the user wants the mode disabled in some mode, the user can
say (setq-local show-paren-mode nil) in the hook for the mode. (And can
check whether it's enabled by just looking at that variable.)
On the other hand, it'd make the mode more regular -- perhaps the user
just wants to switch it on in just a particular buffer.
But we can't really change the names of the global(ized) version of the
mode, because that'd break people's setups. So instead of having a
global-show-paren-mode/show-paren-mode, we'd have
show-paren-mode/show-parent-mode-this-buffer (or something), which is
also pretty confusing.
So taking all that into consideration, I think it'd better to just leave
things as they are, and I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-09-03 6:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 10:28 bug#29381: show-paren-mode should not be globalized Paul Rankin
2017-11-21 10:36 ` Andreas Schwab
2017-11-21 10:45 ` Paul Rankin
2020-08-10 16:14 ` Stefan Kangas
2020-08-12 13:14 ` Phil Sainty
2021-09-03 6:58 ` Lars Ingebrigtsen [this message]
2021-09-03 7:26 ` Paul W. Rankin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-03 7:50 ` Lars Ingebrigtsen
2021-09-09 23:57 ` Dmitry Gutov
2021-09-10 10:52 ` Lars Ingebrigtsen
2021-09-11 2:15 ` Dmitry Gutov
2021-09-11 12:43 ` 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=878s0e402x.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=29381@debbugs.gnu.org \
--cc=hello@paulwrankin.com \
--cc=psainty@orcon.net.nz \
--cc=schwab@suse.de \
--cc=stefan@marxist.se \
/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).