unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 42805@debbugs.gnu.org, Gustavo Tavares Cabral <gustavotcabral@gmail.com>
Subject: bug#42805: 27.1; cc-mode/syntax/font-lock bug
Date: Fri, 27 Aug 2021 19:56:24 +0200	[thread overview]
Message-ID: <87mtp2lqk7.fsf@gnus.org> (raw)
In-Reply-To: <20201123192734.GD4635@ACM> (Alan Mackenzie's message of "Mon, 23 Nov 2020 19:27:34 +0000")

Alan Mackenzie <acm@muc.de> writes:

>> >   When c-multiline-string-start-char is set, font locking breaks after 
>> >   changes in string literals. The issue started after commit 2ca12bb3de:
>> >   I believe that '(c-remove-string-fences (car end-limits))' should be 
>> >   '(c-remove-string-fences (1- (cdr end-limits)))' 
>
>> >   Steps to reproduce: 
>> >     1. Open a .c file; 
>> >     2. Eval '(setq c-multiline-string-start-char ?@)'; 
>> >     3. Delete/insert double quotes. 
>
> I've just done this, and not noticed anything adrift other than
> exceptionally long delays in making the changes.  Would you please state
> more precisely what the problem is that you see.  Thanks!

This was half a year ago, and there was no response (and I can't
reproduce the problem either in 27.1 or the current trunk), so I'm
closing this bug report.  If the problem still exists, please respond to
this email and we'll reopen the bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-08-27 17:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 19:55 bug#42805: 27.1; cc-mode/syntax/font-lock bug Gustavo Tavares Cabral
2020-11-23 17:10 ` Eli Zaretskii
2020-11-23 18:57   ` Alan Mackenzie
2020-11-23 19:27     ` Eli Zaretskii
2020-11-23 19:27   ` Alan Mackenzie
2021-08-27 17:56     ` Lars Ingebrigtsen [this message]

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=87mtp2lqk7.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=42805@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=gustavotcabral@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).