GNU bug report logs - #50462
27.2; emacsclient syntax highlight failure

Previous Next

Full log

Message #11 received at 50462 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: RDS <rds1944 <at> gmail.com>
Cc: 50462 <at> debbugs.gnu.org
Subject: Re: bug#50462: 27.2; emacsclient syntax highlight failure
Date: Wed, 08 Sep 2021 08:48:29 +0300

[Please use Reply All to keep the bug address on the CC list.]

> From: RDS <rds1944 <at> gmail.com>
> Date: Tue, 7 Sep 2021 12:51:16 -0700
> 
> Eli
> 
> Read further into my bug post:
> 
> "Launch emacs as a server. A buffer has a bash or elisp script with font-lock-mode enabled (syntax
> highlighting). It looks just fine. Then, I switch to another buffer & when I return, part of the file is not visible.
> Close inspection shows that only text encoded as strings is rendered black-on-black or
> white-on-white. Disabling font-lock-mode shows nothing is missing! Again enabling font-lock-mode &
> the same text is missing. Killing the buffer & reloading does not fix the problem. At this point opening any new
> bash or elisp file with strings is futile. The only way to correct all is a restart of the daemon! Of course, any
> setup of screens / consoles is lost. However, no data is ever lost or damaged."
> 
> And yes, C-f, C-b are fine. ALL is fine except for string highlight! (.c are ok, org mode are ok, ...)
> 
> Nothing unusual in *Messages*.
> 
> Weird!

So it sounds like the faces lost their colors or something.  When the
problem happens, what does "M-x list-faces-display RET" show for the
font-lock faces: do they appear in their normal colors?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.