From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Latest Cygwin update and Emacs in Mintty
Date: Thu, 15 Jun 2017 10:47:00 -0000 [thread overview]
Message-ID: <40991a4b-1e1c-4d03-f70f-8c77eb29bc7b@cornell.edu> (raw)
In-Reply-To: <87o9tqs8c8.fsf@Rainer.invalid>
On 6/14/2017 3:00 PM, Achim Gratz wrote:
> Achim Gratz writes:
>> After the latest Cygwin update I'm hitting an interesting problem with
>> emacs-nox running in a mintty: when Emacs starts, it decides that the
>> background color is gray instead of the usual white (for all but the
>> rightmost character in the status line, interestingly enough). I have
>> the normal mintty background set slightly off-white (to #F8F8F8) and
>> mintty reports itself as xterm-256color (the same happens in when TERM
>> is set to screen-256color). Emacs starts up with the correct background
>> color, draws the status bar and the menu bar and only then switches the
>> background to gray. The gray it choses is very slightly lighter than
>> the status bar (so lightly in fact that I can make out the difference on
>> only one of my three monitors). Emacs really thinks it is using a white
>> background, as evidenced by the fact that (set-background-color "white")
>> will produce exactly the same result. I get my usual background back
>> with (set-background-color "#F8F8F8"), but I have no idea where the
>> wrong setting for the named color "white" comes from.
>>
>> I'm just trying this at home remotely logging in from a konsole terminal
>> on my Linux box: Here the background chosen is slightly darker than the
>> status bar, the status bar seems to be #B8B8B8 and the background for
>> "white seems to be #B4B4B4. Curious and curiouser...
>
> Ken, did you have a chance to look into this?
Sorry, I must have missed this when you first sent it. I'll take a look.
Ken
--
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-15 10:47 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 [this message]
2017-06-15 13:35 ` Ken Brown
2017-06-15 18:43 ` Brian Inglis
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
2017-06-27 18:55 ` Achim Gratz
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=40991a4b-1e1c-4d03-f70f-8c77eb29bc7b@cornell.edu \
--to=kbrown@cornell.edu \
--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).