From: Deniz Dogan <deniz.a.m.dogan@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-pretest-bug@gnu.org, 5122@emacsbugs.donarmstrong.com
Subject: bug#5122: Mismatched parentheses when dealing with huge buffercontent
Date: Sat, 5 Dec 2009 01:35:09 +0100 [thread overview]
Message-ID: <7b501d5c0912041635r7f71535ap3e8c36995930777e@mail.gmail.com> (raw)
In-Reply-To: <56B6897376CF4A16A9134E0AB7719F32@us.oracle.com>
2009/12/5 Drew Adams <drew.adams@oracle.com>:
>> > See option `blink-matching-paren-distance' and node
>> > Matching in the Emacs manual.
>> > Does increasing that variable's value resolve the problem?
>>
>> Yes, it does solve the problem.
>
> It's not real obvious when you see mismatch highlighting (and are used to it
> working) that the highlighting might not mean a mismatch at all, but just an
> insufficiently large option value. Many (most?) users will not even guess that
> there is such an option.
>
> Perhaps we could use a :help-echo property along with the mismatch highlight
> face, pointing to the option?
>
>
I'm not sure what the best solution would be, but it is indeed strange
that Emacs says that there was a parenthesis *mismatch*. Maybe it
would be better to say something along the lines of "Emacs was unable
to find a matching parenthesis in the previous X characters", but
obviously much more terse.
next prev parent reply other threads:[~2009-12-05 0:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 15:31 bug#5122: Mismatched parentheses when dealing with huge buffer content Deniz Dogan
2009-12-04 22:27 ` bug#5122: Mismatched parentheses when dealing with huge buffercontent Drew Adams
2009-12-05 0:27 ` Deniz Dogan
2009-12-05 0:31 ` Drew Adams
2009-12-05 0:35 ` Deniz Dogan [this message]
2009-12-05 9:27 ` Eli Zaretskii
2009-12-05 16:10 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2009-12-05 20:57 Chong Yidong
2009-12-05 21:42 ` Stefan Monnier
2009-12-05 22:06 ` Chong Yidong
2009-12-05 21:47 ` Eli Zaretskii
2009-12-05 22:11 ` Chong Yidong
2009-12-06 4:03 ` Eli Zaretskii
2009-12-06 15:30 ` Chong Yidong
2009-12-06 17:52 ` Eli Zaretskii
2009-12-06 18:59 ` Chong Yidong
2009-12-07 2:25 ` Stefan Monnier
2011-07-13 14:59 ` Lars Magne Ingebrigtsen
2011-07-13 16:35 ` Drew Adams
2011-07-13 17:26 ` Drew Adams
2009-12-08 21:11 MON KEY
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=7b501d5c0912041635r7f71535ap3e8c36995930777e@mail.gmail.com \
--to=deniz.a.m.dogan@gmail.com \
--cc=5122@emacsbugs.donarmstrong.com \
--cc=drew.adams@oracle.com \
--cc=emacs-pretest-bug@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).