unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>, <5122@emacsbugs.donarmstrong.com>
Cc: deniz.a.m.dogan@gmail.com
Subject: bug#5122: Mismatched parentheses when dealing with huge	buffercontent
Date: Sat, 5 Dec 2009 08:10:37 -0800	[thread overview]
Message-ID: <03B5C6BC7CFA44E6A2033A6153453305@us.oracle.com> (raw)
In-Reply-To: <83ocmdkbxk.fsf@gnu.org>

> > 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?
> 
> help-echo is not guaranteed to be seen, and could be tricky when
> there's an important message in the echo area (especially if the
> help-echo itself is displayed in the echo area).  Also, it will not
> work on a text terminal.
> 
> I think it's better to modify the echo area message, such that if
> Emacs hits the blink-matching-paren-distance limit (as opposed to
> hitting point-min), the message says something like
> 
>   Mismatched parentheses (within blink-matching-paren-distance)

Yes that sounds good too.

To be honest, I don't know if I ever noticed any message in the echo area for
this. Perhaps because the message was so expected I never paid any attention to
it.






  reply	other threads:[~2009-12-05 16:10 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
2009-12-05  9:27       ` Eli Zaretskii
2009-12-05 16:10         ` Drew Adams [this message]
  -- 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=03B5C6BC7CFA44E6A2033A6153453305@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=5122@emacsbugs.donarmstrong.com \
    --cc=deniz.a.m.dogan@gmail.com \
    --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).