From: RDS <rds1944@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 50462@debbugs.gnu.org
Subject: bug#50462: 27.2; emacsclient syntax highlight failure
Date: Wed, 8 Sep 2021 12:21:09 -0700 [thread overview]
Message-ID: <CABj_U1PCNbgDrp8zVMGBSAG5qKDCAxPDhg1VkA=ULbFyUuntow@mail.gmail.com> (raw)
In-Reply-To: <83wnnrknk9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
>So it sounds like the faces lost their color definitions for some
>reason?
Yes. Something overwrote the setting returning it to default state = black.
>When this happens, and you invoke "M-x customize-face" on a
>problematic face, what does Emacs show for the color attributes of the
>face in the Customize buffer?
black.
I then entered green & voila, all was well.
On Wed, Sep 8, 2021 at 10:02 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: RDS <rds1944@gmail.com>
> > Date: Wed, 8 Sep 2021 09:46:38 -0700
> > Cc: Lars Ingebrigtsen <larsi@gnus.org>, 50462@debbugs.gnu.org
> >
> > 1) Using standard agetty, not emacs terminal.
>
> I'm not sure I understand what this means. What is "agetty"? And
> what do you call "emacs terminal"?
>
> > 2) M-x list-faces-display (after fault)
> > All OK except
> > font-lock-string-face (black-on-black)
> > sh-escaped-newline "
> > toolbar "
> > window-divider-last-pixel "
>
> And what happens if you try to customize these faces to define the
> colors they should have? Or different colors? Does that work, or do
> these faces fail to display any colors, no matter what?
>
> Btw, how many colors does this terminal support? You can find the
> answer like this:
>
> M-: (display-color-cells) RET
>
> And finally, does "M-x list-colors-display RET" show some colors
> incorrectly?
>
[-- Attachment #2: Type: text/html, Size: 2335 bytes --]
next prev parent reply other threads:[~2021-09-08 19:21 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
[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 [this message]
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='CABj_U1PCNbgDrp8zVMGBSAG5qKDCAxPDhg1VkA=ULbFyUuntow@mail.gmail.com' \
--to=rds1944@gmail.com \
--cc=50462@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.