unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Istvan Marko <mi-ebugs@kismala.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32072@debbugs.gnu.org
Subject: bug#32072: 27.0.50; clear-face-cache in an X frame breaks tty colors
Date: Mon, 09 Jul 2018 00:17:27 -0700	[thread overview]
Message-ID: <m3h8l8ev3s.fsf@zsu.kismala.com> (raw)
In-Reply-To: <83muv3jwcw.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> Can you tell more about what "messed-up" means?  E.g., what do you see
> if you type "M-x list-colors-display RET" in a TTY frame after
> invoking clear-face-cache on a GUI frame?

Interestingly the colors of list-colors-display remain intact (except
for the modeline). list-faces-display however shows the problem.

Here are some screenshots with the M-x list-faces-display buffer from an
emacs-client -t frame on a 256 color terminal before and after running
clear-face-cache in the X11 frame.

Normal: https://i.imgur.com/QPUbARN.png

Bad: https://i.imgur.com/080IjKI.png

Note that some colors are retained, for example the background of
tty-menu-selected-face which is "red", a color that exists on 16 color
terminals too.

> Or do you mean that a _second_ call to clear-face-cache fixes the TTY
> frames?  

Yes, this. Calling clear-face-cache again, this time from the 256 color
TTY frame, fixes the TTY frames.

> If the latter, does it matter what frame is selected when you issue
> that second call?

Yes, the second call only helps if it's done while the 256 color TTY
frame is the active one.

> What if you invoke clear-face-cache, and then type "M-x redraw-display
> RET" in a TTY frame -- does that still show "messed-up" colors?

M-x redraw-display in the tty frame does not help.

> "Black or green"?  So the effect is not entirely deterministic?

I think it's deterministic but may have a couple of variations depending
on the state of my Emacs session or the terminal. I haven't figured
out

> Do you see this in Emacs 26 as well, or only on the master branch?

Yes, I see this with both 26 and master. I am fairly sure that this
wasn't happening about 2 years ago. Perhaps it started when I switched
from 25 to 26 but not sure. I am having trouble building an old enough
version on my current Linux system to verify but if we get stuck I will
find a way to build it and try to bisect.

-- 
	Istvan





  reply	other threads:[~2018-07-09  7:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 17:18 bug#32072: 27.0.50; clear-face-cache in an X frame breaks tty colors Istvan Marko
2018-07-07  8:14 ` Eli Zaretskii
2018-07-09  7:17   ` Istvan Marko [this message]
     [not found]     ` <m34lgzeje5.fsf@zsu.kismala.com>
2018-07-19  1:39       ` Noam Postavsky
2018-07-19 13:20         ` Eli Zaretskii
2018-07-19 17:33           ` Rami Ylimäki
2018-07-19 17:48             ` Eli Zaretskii
2018-07-19 18:18               ` Istvan Marko
2018-07-19 18:23                 ` Eli Zaretskii

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=m3h8l8ev3s.fsf@zsu.kismala.com \
    --to=mi-ebugs@kismala.com \
    --cc=32072@debbugs.gnu.org \
    --cc=eliz@gnu.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 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).