Re: Latest Cygwin update and Emacs in Mintty

2017-06-17 Thread Achim Gratz
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 #ff. So I guess there's no bug here, just a surprising >

Re: cygwin Digest 17 Jun 2017 08:20:29 -0000 Issue 10294

2017-06-17 Thread Stephen Lyons
I am new to *writing* to mailing lists so if I've done something wrong please forgive me. I would like to "cygport" the Mudlet GPL MUD {Multi-User Dungeon} client to Cygwin - I have a cygport file (and currently a patch) that works to compile a workable binary of the 3.1.0 release available as a

Re: Latest Cygwin update and Emacs in Mintty

2017-06-17 Thread Ken Brown
On 6/17/2017 10:38 AM, Achim Gratz wrote: I don't know why I didn't think of that earlier, but I just fired up emacs-nox from my Linux box and did 'M-x set-background-color RET white RET' and guess what, the background turns a relatively dark shade of grey. I've tried to dig through the call

Re: Latest Cygwin update and Emacs in Mintty

2017-06-17 Thread Achim Gratz
Ken Brown writes: > Even with no .minttrc, 'emacs-nox -Q' followed by 'M-x > set-background-color RET white RET' turns the background gray. I can't rule out that there was a change to the configuration of Emacs on that day that effectively added the set-background operation on that day. > I can

Re: Latest Cygwin update and Emacs in Mintty

2017-06-17 Thread Ken Brown
On 6/17/2017 4:20 AM, Achim Gratz wrote: Ken Brown writes: No, it really was a Cygwin update (to 2.7.0-1). The Emacs update was before that and it had worked right up to that update. Sorry, I misunderstood what you meant by "Cygwin update". I understand now. I'll try to do a bisection of

Re: Latest Cygwin update and Emacs in Mintty

2017-06-17 Thread Achim Gratz
Ken Brown writes: >> No, it really was a Cygwin update (to 2.7.0-1). The Emacs update was >> before that and it had worked right up to that update. > > Sorry, I misunderstood what you meant by "Cygwin update". I > understand now. I'll try to do a bisection of the Cygwin sources. It > may be a