From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Latest Cygwin update and Emacs in Mintty
Date: Thu, 15 Jun 2017 18:43:00 -0000 [thread overview]
Message-ID: <87poe5m6rg.fsf@Rainer.invalid> (raw)
In-Reply-To: <840056d7-6365-97bb-96d0-cca35aaff925@cornell.edu> (Ken Brown's message of "Thu, 15 Jun 2017 09:35:01 -0400")
Ken Brown writes:
> 1. I edited .minttyrc to set
> BackgroundColour=#F8F8F8. (ForegroundColour is 0,0,0, which I guess is
> the default.)
OK.
> 2. I ran 'emacs-nox -Q'. The background color didn't visibly change;
> it's still off-white. The mode line and menu line appear to be
> reversed (black background, off-white foreground, though I can't
> really be sure that the foreground is off-white rather than white).
I think the background gets set to "white" by my .emacs (or rather the
part that customize-options saved).
> 3. I evaluated (set-background-color "white"). This caused the
> background to turn gray. The mode line and menu bar didn't visibly
> change.
That's the main problem and I can't figure out why it associates white with
anything that doesn't have all the bits set in the RGB colorspec.
> 4. I evaluated (set-background-color "#F8F8F8"). The background
> stayed gray.
That's most likely a result of your terminal not being recognized as
being able to use 256 colors.
> I need to investigate 3 and 4, but first I'd like to understand why
> you and I are seeing different things. One difference is the value of
> TERM. You say "mintty reports itself as xterm-256color". Do you mean
> it does this by default, or do you have something in your startup
> files that causes this? When I start mintty, I get the following:
That's an option you can set in mintty or just change the TERM variable
before you start emacs.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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 18:43 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 ` Brian Inglis
2017-06-15 18:43 ` Achim Gratz [this message]
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=87poe5m6rg.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).