all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: John Wiegley <johnw@gnu.org>
Cc: David Reitter <david.reitter@gmail.com>,
	Andrew Hyatt <ahyatt@gmail.com>,
	5560@debbugs.gnu.org
Subject: bug#5560: 23.1.92; parens matching in c-mode broken
Date: Mon, 22 Feb 2016 10:51:04 +0000	[thread overview]
Message-ID: <20160222105104.GB1984@acm.fritz.box> (raw)
In-Reply-To: <m2oab9odin.fsf@newartisans.com>

Hello, John.

On Sun, Feb 21, 2016 at 03:21:52PM -0800, John Wiegley wrote:
> >>>>> David Reitter <david.reitter@gmail.com> writes:

> > I think the question is whether that fix is appropriate for the 25.1
> > release. If you want to apply it there, I would probably test a whole lot of
> > cases in modes that are derivates of c-mode.

> Does this change past behavior? We still have room for fixes in 25.1, but if
> it changes past behavior it will need sufficient testing.

The fix doesn't change past behaviour, beyond fixing the actual bug.
What is amazing is that on doing a triple click with mouse-1 on such an
unmatched paren, an error is signaled after the second click, but Emacs
then goes on to mark the line correctly after the third click.

> -- 
> John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
> http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2016-02-22 10:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11  3:01 bug#5560: 23.1.92; parens matching in c-mode broken David Reitter
2016-02-17  3:56 ` Andrew Hyatt
2016-02-20 22:57   ` Alan Mackenzie
2016-02-21 12:35     ` Alan Mackenzie
2016-02-21 21:40       ` David Reitter
2016-02-21 23:21         ` John Wiegley
2016-02-22 10:51           ` Alan Mackenzie [this message]
2016-02-22 10:35         ` Alan Mackenzie
2016-02-22 12:09           ` David Reitter
2016-02-25  9:54             ` Alan Mackenzie

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=20160222105104.GB1984@acm.fritz.box \
    --to=acm@muc.de \
    --cc=5560@debbugs.gnu.org \
    --cc=ahyatt@gmail.com \
    --cc=david.reitter@gmail.com \
    --cc=johnw@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 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.