From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 50895@debbugs.gnu.org, Jim Porter <jporterbugs@gmail.com>
Subject: bug#50895: 28.0.50; show-paren-mode is distracting in some modes
Date: Thu, 30 Sep 2021 08:45:48 +0200 [thread overview]
Message-ID: <87pmsq5zoj.fsf@gnus.org> (raw)
In-Reply-To: <7867800d-f770-0316-6659-7ff6f310cd57@yandex.ru> (Dmitry Gutov's message of "Wed, 29 Sep 2021 23:02:03 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> Unlike font-lock-global-mode, it seems in this case the code will be
> checking show-paren-global-modes at runtime (inside
> show-paren-function, I guess).
Looking at show-paren-mode again -- I thought we'd agreed to make it a
globalized minor mode instead of a global minor mode? I.e., define it
with `define-globalized-minor-mode'. Did that prove to be difficult to
do (i.e., not backwards-compatible)?
If we do that, then we'd define it exactly like global-font-lock-mode is
defined (with the turn-on-paren-mode-if-desired logic).
> The new var, if we add it now, should probably be just t by default.
>
> To avoid changing the behavior for those who customized
> show-paren-mode for many years, and yet allow an easy customization
> point for others who can by annoyed with the change.
I don't see why the default value of a new `paren-mode-global-modes'
variable would affect people who are saying (show-paren-mode 1) in their
init files? It should only affect those who haven't made any such
customisation already.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-09-30 6:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 17:25 bug#50895: 28.0.50; show-paren-mode is distracting in some modes Lars Ingebrigtsen
2021-09-29 17:54 ` bug#50895: [External] : " Drew Adams
2021-09-29 17:59 ` Jim Porter
2021-09-29 18:01 ` Lars Ingebrigtsen
2021-09-29 20:02 ` Dmitry Gutov
2021-09-30 6:45 ` Lars Ingebrigtsen [this message]
2021-09-30 11:19 ` Dmitry Gutov
2021-09-30 13:39 ` Lars Ingebrigtsen
2021-09-30 17:00 ` Dmitry Gutov
2021-10-01 7:30 ` Lars Ingebrigtsen
2021-09-30 9:02 ` Eli Zaretskii
2021-09-30 9:26 ` Lars Ingebrigtsen
2021-09-30 10:02 ` Eli Zaretskii
2021-09-30 17:03 ` Dmitry Gutov
2021-09-29 18:02 ` Eli Zaretskii
2021-09-29 18:03 ` Lars Ingebrigtsen
2021-09-29 18:11 ` bug#50895: [External] : " Drew Adams
2021-09-29 18:25 ` Eli Zaretskii
2021-09-29 18:31 ` Lars Ingebrigtsen
2021-09-29 18:40 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2021-09-29 17:10 bug#50894: Disable show-paren-mode in special modes Juri Linkov
2022-09-02 12:23 ` bug#50895: 28.0.50; show-paren-mode is distracting in some modes 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=87pmsq5zoj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50895@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=jporterbugs@gmail.com \
/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).