unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rahguzar@zohomail.eu, dgutov@yandex.ru, 61098@debbugs.gnu.org
Subject: bug#61098: 29.0.60; Confusing behavior of show-paren-mode
Date: Sun, 05 Feb 2023 10:19:24 -0500	[thread overview]
Message-ID: <jwvbkm8jgap.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83k011z38k.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 01 Feb 2023 19:48:11 +0200")

> I guess I don't understand what show-paren-local-mode does, then.  Let
> me explain my line of reasoning:
>
>   (define-minor-mode show-paren-local-mode
>     "Toggle `show-paren-mode' only in this buffer."
>     :variable ( show-paren-mode .
> 		(lambda (val) (setq-local show-paren-mode val)))
>     (cond
>      ((eq show-paren-mode (default-value 'show-paren-mode))
>       (unless show-paren-mode
> 	(show-paren--delete-overlays))
>       (kill-local-variable 'show-paren-mode))
>      ((not (default-value 'show-paren-mode))
>       ;; Locally enabled, but globally disabled.
>       (show-paren-mode 1)                ; Setup the timer.
>       (setq-default show-paren-mode nil) ; But keep it globally disabled.
>       )
>      (t ;; Locally disabled only.
>       (show-paren--delete-overlays))))
>
> When I looked at the above function and stepped through it in the OP's
> scenario, what I saw was that the 2nd condition of 'cond' doesn't
> fire, because the default-value of show-paren-mode is t nowadays.  So
> I concluded that this code relies on the mode being globally off by
> default, and attempted to fix the condition that turns the mode on
> locally even though it is on globally.

But if the mode is already globally enabled, the (setq-default show-paren-mode nil)
will definitely not be right: you'd end up disabling it globally (while
maybe keeping it enabled locally).

> The predicate used by the timer requires either a match of the buffer
> (which doesn't happen in this case) or that the local value of
> show-paren-mode is non-nil.  Setting the local value non-nil is the
> job of the mode function, isn't it?

Yes, but the first branch of the `cond` incorrectly does
`kill-local-variable` under the assumption that the local value doesn't
matter if it's the same as the global one, but that's not true here
because (as a wise man said):

   The predicate used by the timer requires either a match of the buffer
   (which doesn't happen in this case) or that the local value of
   show-paren-mode is non-nil.


-- Stefan






  reply	other threads:[~2023-02-05 15:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 16:03 bug#61098: 29.0.60; Confusing behavior of show-paren-mode Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-28 12:20 ` Eli Zaretskii
2023-01-30 19:21   ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-31 12:03     ` Eli Zaretskii
2023-01-31 13:03       ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-31 14:13         ` Eli Zaretskii
2023-01-31 14:41           ` Dmitry Gutov
2023-01-31 22:42       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-01 17:48         ` Eli Zaretskii
2023-02-05 15:19           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-05 15:24             ` Eli Zaretskii
2023-02-05 17:21               ` Dmitry Gutov
2023-02-05 18:29                 ` Eli Zaretskii
2023-02-05 19:06                   ` Dmitry Gutov
2023-02-05 18:57                 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-05 19:09                   ` Dmitry Gutov
2023-01-31  2:37   ` Dmitry Gutov

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=jwvbkm8jgap.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=61098@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rahguzar@zohomail.eu \
    /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).