From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Latest Cygwin update and Emacs in Mintty
Date: Sat, 17 Jun 2017 21:04:00 -0000 [thread overview]
Message-ID: <8737ay72c9.fsf@Rainer.invalid> (raw)
In-Reply-To: <0954cb04-9534-b058-fc0a-f0abf6dc3271@cornell.edu> (Ken Brown's message of "Sat, 17 Jun 2017 13:54:11 -0400")
Ken Brown writes:
> OK, so it's not a Cygwin issue. And I just learned about M-x
> list-colors-display. If you try this in emacs-nox in Mintty with
> TERM=xterm-256color, you'll see that white is #e5e5e5 and brightwhite
> is #ffffff. So I guess there's no bug here, just a surprising
> definition of "white".
Yes. I'll have to figure out just why it tries to set the background to
the named color "white" on startup, then. That must have got saved as
an option somewhere, maybe I can still find an old enough backup to
compare the startup files to.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-06-17 21:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 17:47 Achim Gratz
2017-06-14 19:00 ` Achim Gratz
2017-06-15 10:47 ` Ken Brown
2017-06-15 13:35 ` Ken Brown
2017-06-15 18:43 ` Achim Gratz
2017-06-15 21:48 ` Ken Brown
2017-06-16 18:27 ` Achim Gratz
2017-06-16 23:46 ` Ken Brown
2017-06-17 8:20 ` Achim Gratz
2017-06-17 12:58 ` Ken Brown
2017-06-17 14:38 ` Achim Gratz
2017-06-17 17:54 ` Ken Brown
2017-06-17 21:04 ` Achim Gratz [this message]
2017-06-27 18:55 ` Achim Gratz
2017-06-15 18:43 ` Brian Inglis
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=8737ay72c9.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.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.
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).