From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: arash@gnu.org, 51032@debbugs.gnu.org, mardani29@yahoo.es
Subject: bug#51032: 29.0.50; Choices for blink-matching-paren
Date: Wed, 6 Oct 2021 14:57:09 -0400 [thread overview]
Message-ID: <CADwFkmnmdKFKv4a3Skac7M-WXJmdYqZP3d6V7WQ9B+CaOEHMsQ@mail.gmail.com> (raw)
In-Reply-To: <8335pe2es6.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> +In addition, if the opening paren is not visible on screen, show
>> +its position in the echo area.
>
> But that's incorrect, because it doesn't happen when the value is
> 'jump' or 'jump-offscreen'. The "in addition" part makes it sound
> like it happens with any non-nil value.
The exception you mention is listed immediately below, so I don't see
how it could be considered incorrect.
> How many possible values can this variable have, and how many are
> listed in the menu of choices that will be presented to the user?
I don't follow. Do you want to change non-nil to t in the docstring?
next prev parent reply other threads:[~2021-10-06 18:57 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 [this message]
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
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=CADwFkmnmdKFKv4a3Skac7M-WXJmdYqZP3d6V7WQ9B+CaOEHMsQ@mail.gmail.com \
--to=stefan@marxist.se \
--cc=51032@debbugs.gnu.org \
--cc=arash@gnu.org \
--cc=eliz@gnu.org \
--cc=mardani29@yahoo.es \
/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.