From: Alan Mackenzie <acm@muc.de>
To: npostavs@users.sourceforge.net
Cc: 7918@debbugs.gnu.org
Subject: bug#7918: [PATCH] cc-mode: only the first clause of a for-loop should be checked for declarations
Date: Mon, 3 Jul 2017 20:18:08 +0000 [thread overview]
Message-ID: <20170703201808.GA3875@acm> (raw)
In-Reply-To: <87mv8li9s7.fsf@users.sourceforge.net>
Hello, Noam and Glenn.
On Mon, Jul 03, 2017 at 15:46:00 -0400, npostavs@users.sourceforge.net wrote:
> Glenn Morris <rgm@gnu.org> writes:
> > npostavs@users.sourceforge.net wrote:
> >>> Bug fixed in master branch.
> >> I can confirm it's fixed in master (I wonder why the bug was reopened,
> >> apparently automatically?)
> > Nothing gets reopened automatically. I agree that sometimes debbugs
> > doesn't report the details of control requests in an informative way.
> > In this case, the bug was reopened in May 2016 (by Alan, from internal
> > logs). You'd have to ask him why.
It was because the original "fix" for the bug slowed CC Mode's
fontification down by a factor of ~3.
> > http://lists.gnu.org/archive/html/emacs-bug-tracker/2016-05/msg00126.html
> Oh, I was looking at
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=7918;msg=32. So all those
> "fake control message" things are just the original control request
> getting lost somehow?
> Ccing Alan, please reopen if I made a mistake by closing this.
This is strange. I sent an email attempting to close the bug for a
second time on 2016-05-16. This email was actually received and
acknowledged by debbugs.gnu.org. But apparently the bug didn't get
closed. Maybe sending mail to 7918-done@debbugs.gnu.org only works the
first time around.
Anyway, it's fine for the bug finally to be marked closed. Thanks.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-07-03 20:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 6:36 bug#7918: [PATCH] cc-mode: only the first clause of a for-loop should be checked for declarations Daniel Colascione
2016-02-26 6:18 ` Lars Ingebrigtsen
2016-02-26 6:31 ` Daniel Colascione
2016-02-26 6:33 ` Daniel Colascione
2016-03-01 18:02 ` Alan Mackenzie
2016-03-01 18:05 ` Daniel Colascione
2016-04-01 16:18 ` Alan Mackenzie
2016-04-25 18:04 ` Alan Mackenzie
[not found] ` <handler.7918.D7918.146160769022226.notifdone@debbugs.gnu.org>
2017-06-29 1:06 ` npostavs
2017-07-03 19:09 ` Glenn Morris
2017-07-03 19:46 ` npostavs
2017-07-03 20:18 ` Alan Mackenzie [this message]
2017-07-05 15:55 ` Glenn Morris
2017-07-05 20:14 ` Alan Mackenzie
2017-07-06 1:39 ` Glenn Morris
2017-07-07 14:47 ` 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=20170703201808.GA3875@acm \
--to=acm@muc.de \
--cc=7918@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).