unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>
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 20:00:41 +0300	[thread overview]
Message-ID: <7535661b-a9e8-d5f6-c156-bf39a394255b@yandex.ru> (raw)
In-Reply-To: <877dey2ndr.fsf@gnus.org>

On 30.09.2021 16:39, Lars Ingebrigtsen wrote:
> Dmitry Gutov <dgutov@yandex.ru> writes:
> 
>> The value of font-lock-global-modes affects how global-font-lock-mode works.
> 
> Right.  But we could make (show-paren-mode 1) set the mooted
> show-paren-global-modes to t.  Since it's show-paren-mode is on by
> default, show-paren-global-modes would basically only be used by those
> people who's not explicitly saying (show-paren-mode 1).
> 
> And (show-paren-mode -1), for that matter.
> 
> So introducing a variable like that (with a default value of `(not
> special-mode)') should not affect people who are already explicitly
> switching the mode on or off.
> 
> Or am I missing something?

That should be doable, yes.

I just can't think of another mode that does something similar. So this 
kind of special behavior might catch people by surprise.

Anyway, this is not a strong objection, and I might be convinced by a 
particular implementation. We could even adopt this practice in more 
places, if it really makes sense to people.

At the moment, though, I'm more in favor of adding a *-global-modes 
variable, and then, having collected feedback, changing its default in 
some future version.





  reply	other threads:[~2021-09-30 17:00 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
2021-09-30 11:19         ` Dmitry Gutov
2021-09-30 13:39           ` Lars Ingebrigtsen
2021-09-30 17:00             ` Dmitry Gutov [this message]
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=7535661b-a9e8-d5f6-c156-bf39a394255b@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=50895@debbugs.gnu.org \
    --cc=jporterbugs@gmail.com \
    --cc=larsi@gnus.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).