unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Eli Zaretskii" <eliz@gnu.org>, "Géza Herman" <geza.herman@gmail.com>
Cc: 70435@debbugs.gnu.org
Subject: bug#70435: 30.0.50; cc-mode: <> are sometimes not reconized as parentheses
Date: Thu, 2 May 2024 10:24:23 +0000	[thread overview]
Message-ID: <ZjNp16i3Y7C9zfJ5@ACM> (raw)
In-Reply-To: <8634r0muh3.fsf@gnu.org>

Hello, Eli and Géza.

On Thu, May 02, 2024 at 12:30:32 +0300, Eli Zaretskii wrote:
> > From: Herman, Géza <geza.herman@gmail.com>
> > Cc: Herman Géza <geza.herman@gmail.com>,
> >  70435@debbugs.gnu.org, Eli
> >  Zaretskii <eliz@gnu.org>
> > Date: Mon, 29 Apr 2024 19:21:01 +0200


> > Hello Alan,

> > Alan Mackenzie <acm@muc.de> writes:

> > > I have a fix, I think.  It is actually a two line fix, removing 
> > > a test
> > > from the top of a function, but it involves reindenting the 
> > > entire rest
> > > of the function.

> > > Please apply the patch below, recompile cc-engine.el, then load 
> > > the
> > > resulting CC Mode into a running Emacs.  Please test it on your 
> > > real C++
> > > code, and let me know if the bug is actually fixed.  Thanks!

> > I can confirm that the patch fixes the issue, I tested it in real 
> > circumstances.

> > Thanks for fixing the problem so quickly!

> Alan, should this bug be closed now?

Apologies for my dithering.  I've been having second thoughts about the
patch in the last few days, and wondering whether I should refine it.

It's all to do with a function c-unmark-<>-around-region, which was run
in before-change-functions for a deletion, and after-change-functions for
an insertion.  The patch I sent to Géza made that function run in before-
and after-c-f both for insertions and deletions.

I've been wondering whether that is strictly necessary, since it will
slow down CC Mode a little.  I'm thinking that in the
insertion/before-c-f case, I might not need the call.

Géza, would you be prepared to do a little more testing if I modified the
patch?

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2024-05-02 10:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 10:47 bug#70435: 30.0.50; cc-mode: <> are sometimes not reconized as parentheses Herman, Géza
2024-04-27  8:33 ` Eli Zaretskii
2024-04-27 10:08   ` Alan Mackenzie
2024-04-28 15:44 ` Alan Mackenzie
2024-04-28 16:47   ` Herman, Géza
2024-04-28 20:31     ` Alan Mackenzie
2024-04-29 15:53     ` Alan Mackenzie
2024-04-29 17:21       ` Herman, Géza
2024-05-02  9:30         ` Eli Zaretskii
2024-05-02 10:24           ` Alan Mackenzie [this message]
2024-05-02 12:49             ` Herman, Géza
2024-05-02 13:16               ` bug#70435: 30.0.50; cc-mode: <> are sometimes not recognized " Alan Mackenzie
2024-05-02 19:58                 ` Herman, Géza
2024-05-05 11:55                   ` 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

  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=ZjNp16i3Y7C9zfJ5@ACM \
    --to=acm@muc.de \
    --cc=70435@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=geza.herman@gmail.com \
    /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).