all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark Oteiza <mvoteiza@udel.edu>
To: 20240@debbugs.gnu.org
Subject: bug#20240: 25.0.50; CC Mode broken fontification and commenting
Date: Wed, 01 Apr 2015 16:04:59 -0400	[thread overview]
Message-ID: <871tk34ntg.fsf@udel.edu> (raw)
In-Reply-To: <20150401192139.20032.qmail@mail.muc.de> (Alan Mackenzie's message of "1 Apr 2015 19:21:39 -0000")

Alan Mackenzie <acm@muc.de> writes:

> In article <mailman.3120.1427885528.31049.bug-gnu-emacs@gnu.org> you wrote:
>>>From emacs -Q:
>
>> 1. C-x C-f foo.c RET
>> 2. Insert: { RET }
>> 3. Select the first line and M-;
>
>> Only `/* ` is inserted at the beginning of the buffer, which is wrong.
>
> It actually signals an error at that point, which is indeed wrong.

Ah, I missed it then, thanks.

> I've just committed a fix to the Emacs repository.  Could you please update
> your sources, rebuild, and confirm that the fix works, please.
>
> Thanks for taking the trouble to report this bug.

You're welcome. You fixed the example I gave, but as it turns out my
example was too minimal. Hopefully this is better: uncommenting the
commented line in the following will signal a jit-lock error

int main(void) {
  for(;;) {
    /* return 0; */
  }
}

Repeating M-; on that line, eventually I get `return 0;` uncommented but
fontified as a comment.





  reply	other threads:[~2015-04-01 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 10:51 bug#20240: 25.0.50; CC Mode broken fontification and commenting Mark Oteiza
     [not found] ` <mailman.3120.1427885528.31049.bug-gnu-emacs@gnu.org>
2015-04-01 19:21   ` Alan Mackenzie
2015-04-01 20:04     ` Mark Oteiza [this message]
     [not found] ` <mailman.3163.1427918769.31049.bug-gnu-emacs@gnu.org>
2015-04-03 20:52   ` Alan Mackenzie
2015-04-03 22:09     ` Stefan Monnier
2015-04-04 10:45       ` Alan Mackenzie
2015-04-04 14:47         ` Mark Oteiza

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=871tk34ntg.fsf@udel.edu \
    --to=mvoteiza@udel.edu \
    --cc=20240@debbugs.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.