From: Eli Zaretskii <eliz@gnu.org>
To: RDS <rds1944@gmail.com>
Cc: 50462@debbugs.gnu.org
Subject: bug#50462: 27.2; emacsclient syntax highlight failure
Date: Tue, 07 Sep 2021 21:36:16 +0300 [thread overview]
Message-ID: <83sfygnsgv.fsf@gnu.org> (raw)
In-Reply-To: <CABj_U1N=nGBamzt6_B3kGivpc=Rc+iDGC4=Q6qG_q_hoqT1-tw@mail.gmail.com> (message from RDS on Tue, 7 Sep 2021 11:11:20 -0700)
> From: RDS <rds1944@gmail.com>
> Date: Tue, 7 Sep 2021 11:11:20 -0700
>
> Initially everything behaves as expected in console & X. Then on time scales ranging from minutes to hours
> with the various emacsclients, randomly switching among tty's & killing / loading buffers, I eventually see
> that .bashrc is displayed with "missing" chars.
Are they really missing, or just displayed with the same foreground
and background colors? What happens if you move the cursor (with C-f
or C-b) across the "missing" text?
Also, do you see any error messages in the *Messages* buffer when this
happens?
next prev parent reply other threads:[~2021-09-07 18:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 18:11 bug#50462: 27.2; emacsclient syntax highlight failure RDS
2021-09-07 18:36 ` Eli Zaretskii [this message]
[not found] ` <CABj_U1OXrP0keeSGaUN9SPFR=cDsMShVYbNXuPwzXD78kL51fg@mail.gmail.com>
2021-09-08 5:48 ` Eli Zaretskii
2021-09-08 6:54 ` Lars Ingebrigtsen
2021-09-08 7:51 ` Eli Zaretskii
2021-09-08 16:46 ` RDS
2021-09-08 17:02 ` Eli Zaretskii
2021-09-08 17:28 ` RDS
2021-09-08 18:54 ` Eli Zaretskii
2021-09-08 17:33 ` RDS
2021-09-08 19:21 ` RDS
2021-09-08 19:25 ` Eli Zaretskii
2021-09-08 20:05 ` RDS
2021-09-08 20:17 ` Eli Zaretskii
2021-09-08 20:32 ` RDS
2021-09-09 5:34 ` Eli Zaretskii
2021-09-09 13:56 ` Lars Ingebrigtsen
2021-09-09 18:56 ` RDS
2021-09-09 19:02 ` Lars Ingebrigtsen
2021-09-09 19:06 ` Eli Zaretskii
2021-09-08 16:53 ` RDS
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=83sfygnsgv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50462@debbugs.gnu.org \
--cc=rds1944@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 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.