all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 51032@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>,
	mardani29@yahoo.es
Subject: bug#51032: 29.0.50; Choices for blink-matching-paren
Date: Thu, 07 Oct 2021 12:17:01 +0200	[thread overview]
Message-ID: <861r4xta02.fsf@gnu.org> (raw)
In-Reply-To: <43de1228-5ce6-53a2-d469-e62110445d11@gmx.at> (martin rudalics's message of "Thu, 7 Oct 2021 11:34:08 +0200")

martin rudalics <rudalics@gmx.at> writes:

>> "any other non-nil value" will act like t -- this is at least my
>> understanding.
>
> Then we probably should say so.  But how does 'blink-matching-paren'
> interact with 'blink-matching-paren-on-screen' non-nil (in particular
> when 'blink-matching-paren' is 'jump')?  I'm completely ignorant here.

Then we are 2.

> 'blink-matching-paren-on-screen' is not documented, its doc-string says
>
> "Non-nil means show matching open-paren when it is on screen."

The second sentence reads:

    If nil, don’t show it (but the open-paren can still be shown
    in the echo area when it is off screen).

My reading is this variable gives you more control in terms of: Don't
highlight the open-paren if on-screen (either jump or highlight), but do
if off-screen, i.e., show the position in the echo area.  But I think it
breaks for this combination:

    (setq blink-matching-paren 'jump-offscreen)
    (setq blink-matching-paren-on-screen nil)

which does nothing.  But that's another bug report from someone more
knowledgeable.

> In either case your proposal looks good to me.

Thanks, but Eli's patch is even better :)

Best, Arash





  reply	other threads:[~2021-10-07 10:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 12:18 bug#51032: 29.0.50; Choices for blink-matching-paren Arash Esbati
2021-10-05 14:25 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-05 21:23   ` Stefan Kangas
2021-10-06 12:06     ` Eli Zaretskii
2021-10-06 18:10       ` Stefan Kangas
2021-10-06 18:23         ` Eli Zaretskii
2021-10-06 18:57           ` Stefan Kangas
2021-10-06 19:05             ` Eli Zaretskii
2021-10-06 20:53               ` Stefan Kangas
2021-10-07  9:02                 ` Arash Esbati
2021-10-07  9:08                   ` martin rudalics
2021-10-07  9:16                     ` Arash Esbati
2021-10-07  9:34                       ` martin rudalics
2021-10-07 10:17                         ` Arash Esbati [this message]
2021-10-07 13:49                           ` Eli Zaretskii
2021-10-07  9:39                   ` Eli Zaretskii
2021-10-07 10:20                     ` Arash Esbati
2021-10-07  9:36                 ` Eli Zaretskii
2021-10-07 13:05                   ` Stefan Kangas
2021-10-07 13:20                     ` Eli Zaretskii
2021-10-05 17:10 ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=861r4xta02.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=51032@debbugs.gnu.org \
    --cc=mardani29@yahoo.es \
    --cc=rudalics@gmx.at \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.