unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 58578@debbugs.gnu.org
Subject: bug#58578: 29.0.50; Font lock randomly breaks in some buffers and gets worse over time
Date: Mon, 17 Oct 2022 11:20:01 +0300	[thread overview]
Message-ID: <83pmeq3lqm.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkxNobg6Lr9hYZ18uUZRBPGUuzgg19-Zb+aCFPutxTdwQ@mail.gmail.com> (message from Stefan Kangas on Mon, 17 Oct 2022 07:27:56 +0000)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Mon, 17 Oct 2022 07:27:56 +0000
> 
> Stefan Kangas <stefankangas@gmail.com> writes:
> 
> > Here is a screenshot from `notmuch-message-mode', based on
> > `message-mode':
> 
> For a while, I could reproduce the incorrect fontification in a
> `notmuch-message-mode' buffer after replying to an email.
> 
> Everything looks fine when I first create the buffer.  But when I move
> point to the end of some quoted line, and press RET (`newline'), there
> is incorrect fontification on the new line, and I see:
> 
>      There are text properties here:
>        face                 message-cited-text-1
>        fontified            t
> 
> (It looks like in the screenshot in the last email.)
> 
> If I go to the beginning of another line and press C-o (`open-line'), the
> fontification is correct, and there is no face property on the new line:
> 
>      There are text properties here:
>        fontified            t
> 
> Why would `newline' and `open-line' lead to different results?
> It seems very strange to me.
> 
> [time passes]
> 
> What is even stranger is that now, an hour or two later, I can no longer
> reproduce this behavior, not in the same session and not even in the same
> buffers as before.  The incorrect fontification only still remains on the same
> lines as before, however.
> 
> I did no particular changes that should affect this.  I was just sending emails
> and doing some unrelated ELisp coding.
> 
> Should I start looking at my timers here, or something?

Maybe.  Or maybe this is specific to notmuch-message-mode.

I would suggest to focus on more popular modes.





  reply	other threads:[~2022-10-17  8:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  4:40 bug#58578: 29.0.50; Font lock randomly breaks in some buffers and gets worse over time Stefan Kangas
2022-10-17  6:42 ` Eli Zaretskii
2022-10-17  7:27 ` Stefan Kangas
2022-10-17  8:20   ` Eli Zaretskii [this message]
2023-09-10 23:53     ` Stefan Kangas

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=83pmeq3lqm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58578@debbugs.gnu.org \
    --cc=stefankangas@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).