From: Arash Esbati <arash@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51032@debbugs.gnu.org, stefan@marxist.se, mardani29@yahoo.es
Subject: bug#51032: 29.0.50; Choices for blink-matching-paren
Date: Thu, 07 Oct 2021 12:20:06 +0200 [thread overview]
Message-ID: <86wnmprvah.fsf@gnu.org> (raw)
In-Reply-To: <83a6jl18du.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 07 Oct 2021 12:39:25 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Arash Esbati <arash@gnu.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>, mardani29@yahoo.es, 51032@debbugs.gnu.org
>> Date: Thu, 07 Oct 2021 11:02:23 +0200
>>
>> I think the values in the value menu are Ok, the only misleading part of
>> docstring was
>>
>> With any other non-nil value, the off-screen position of the opening
>> paren will be shown in the echo area.
>
> It is IMO wrong to have that text there, because 'jump-offscreen'
> doesn't do that, and 'jump' does it only of the open-paren is
> off-screen.
Agreed.
> Please take a look at the changes I just installed: are they OK?
LGTM. Thanks for the clarification.
Best, Arash
next prev parent reply other threads:[~2021-10-07 10:20 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
2021-10-07 13:49 ` Eli Zaretskii
2021-10-07 9:39 ` Eli Zaretskii
2021-10-07 10:20 ` Arash Esbati [this message]
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
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=86wnmprvah.fsf@gnu.org \
--to=arash@gnu.org \
--cc=51032@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mardani29@yahoo.es \
--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 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).