From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Antero Mejr <antero@mailbox.org>
Cc: 68234@debbugs.gnu.org
Subject: bug#68234: [PATCH] Increase blink-matching-paren-distance by 300kb.
Date: Sat, 6 Jan 2024 04:09:14 -0800 [thread overview]
Message-ID: <CADwFkm=p0uA_bxqTQCBQQ3ecWyXBrmHi24zrBzNkHfncOYQBMg@mail.gmail.com> (raw)
In-Reply-To: <83y1d3t06t.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> AFAIU, this will show nothing when the matching parenthesis is not
> found? If so, why is that a good idea?
I guess the point is to avoid false positives: Emacs confidently says
"no matching paren", but actually there is one. We just didn't try hard
enough to find it.
On the other hand, perhaps we could just adjust the message to make it
more clear: "no matching parenthesis within 100000 characters" or
something like that (but only if the buffer is indeed longer). (But
then I wouldn't bother with the (* 100 1024) part, and just do 100000 or
200000 outright to improve the display. This is a nit though.)
next prev parent reply other threads:[~2024-01-06 12:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 18:37 bug#68234: [PATCH] Increase blink-matching-paren-distance by 300kb Antero Mejr via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <handler.68234.B.170430710530123.ack@debbugs.gnu.org>
2024-01-03 18:48 ` Antero Mejr via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-04 11:31 ` Eli Zaretskii
2024-01-04 23:08 ` Stefan Kangas
2024-01-05 7:49 ` Eli Zaretskii
2024-01-05 20:50 ` Antero Mejr via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-05 21:10 ` Antero Mejr via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-06 7:01 ` Eli Zaretskii
2024-01-06 12:09 ` Stefan Kangas [this message]
2024-01-09 5:56 ` Stefan Kangas
2024-01-04 4:50 ` Stefan Kangas
2024-01-04 19:22 ` Antero Mejr via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-04 21:03 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-04 21:36 ` Antero Mejr via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CADwFkm=p0uA_bxqTQCBQQ3ecWyXBrmHi24zrBzNkHfncOYQBMg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=68234@debbugs.gnu.org \
--cc=antero@mailbox.org \
--cc=eliz@gnu.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).