X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:subject:references:date:in-reply-to :message-id:mime-version:content-type; q=dns; s=default; b=T917J c/+ab9NUpNeuM8QBgeyCX7zbiBIQ55ovK10v2kgs7EQN8NdBJc5fldB71hVHx/AS V+cUK0q4o367YU9GHaw7FNM4hoNnW37nUhSA5nM2yeL1alGtRKT3eK7bUCSxfGwj M1jKGUOrX2hModwotQmU2Ra5g8v+5IVcUbqeoA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:subject:references:date:in-reply-to :message-id:mime-version:content-type; s=default; bh=GzrofuMHaYz ul3LrMDwmiNadwfM=; b=csxtA0OcjSqmqTwfZKUNguteDLKvWNmjSz8LCNfzsMe fD+oMkdb9kIj137EgEsW5YxijG8GhSGnkC/T0Gv+oRe3/iQAC8UdHfwQUCsFn1en bQhtkTUh0ynhVEgbM2x+k01frZLcSTtYYibNUhS8cSgfPdhL24x40MFsQKhue3/g = Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_40,SPF_PASS autolearn=ham version=3.3.2 spammy=gray, TERM, mintty, Singles X-HELO: vsmx012.vodafonemail.xion.oxcs.net From: Achim Gratz To: cygwin AT cygwin DOT com Subject: Re: Latest Cygwin update and Emacs in Mintty References: <87wpciktid DOT fsf AT Rainer DOT invalid> Date: Wed, 14 Jun 2017 21:00:23 +0200 In-Reply-To: <87wpciktid.fsf@Rainer.invalid> (Achim Gratz's message of "Wed, 22 Feb 2017 18:47:06 +0100") Message-ID: <87o9tqs8c8.fsf@Rainer.invalid> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-VADE-STATUS: LEGIT 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? 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