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
> 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



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 tarball
from https://github.com/Mudlet/Mudlet/archive/Mudlet-3.1.0.tar.gz {other
distribution methods are available!} but Mudlet possesses a Lua
sub-system that users/MUD system operators can use to provide additional
functionality and this is currently proving awkward!

The issue I am having is that Mudlet needs some Lua "modules" to operate
and Cygwin currently only provides a sub-set of the needed ones, the
lua-file-system "lfs" IS available but also needed is:

* "rex_pcre"

* "zip"

* "luasql.sqlite3"

What is the best way to get those "run-time" dependencies into Cygwin? I
have found "luarocks" packaged versions (as "lrexlib-pcre", "luazip" and
"luasql-sqlite3" respectly) but it is not immediately apparent how I
might use that to generate the things needed as part of the "cygport"
process.

For the record Mudlet {https://www.mudlet.org} is carried on, at least,
the Debian & Ubuntu GNU/Linux distributions and it's developers do
target and aim to provide Linux, macOs and Window platform binaries as
well as source code. However the Windows one does suffer a little in
bug-fixes and performance because it is difficult to put together a
development platform (IMHO) for that OS that will work in both a 32 and
a 64 bit environment (as until very recently) the Qt people only made a
32 bit FOSS development environment available with a built-in Mingw
compiler and, of course, the alternative free MSVC compiler can not be
used to make binaries that can be distributed under GPL terms; the need
to compile/source the other libraries that Mudlet uses in a form that is
compatible with anything compiled with such a Qt/Mingw combination makes
the Cygwin environment much more user friendly for normally *nix system
based developers...

I should perhaps point out that I *am* one of the "upstream" i.e. a
member of the team that call ourselves the "Mudlet-makers" and I have
been using Cygwin on and off for years now... 8-)

I do miss the Qt Creator IDE when I switch to the Cygwin environment
though. 8-(

Stephen




signature.asc
Description: OpenPGP digital signature


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 chain that would lead to that
result and it seems that the result depends on whether brightwhite/15 or
white/7 gets picked from tty-color-alist or a value gets generated from
tty-color-standard-values (which uses the X definitions for the named
colors).


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 definition 
of "white".


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



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 also reproduce the
> problem in xterm, so I don't think Mintty is the culprit.

I already said in my original report that I can reproduce this from my
Linux box via konsole.

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 chain that would lead to that
result and it seems that the result depends on whether brightwhite/15 or
white/7 gets picked from tty-color-alist or a value gets generated from
tty-color-standard-values (which uses the X definitions for the named
colors).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
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



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 the Cygwin sources.  It
may be a few days before I get to this.


It may be possible that the coreutils update messed up things in a way
that I don't understand, but that's unlikely.  Or vim might have
delivered a file that conflicts with something from Emacs, but Emacs has
since been updated again and so that conflict would have flipped in
favor of Emacs at those times, which I didn't observe (and no such
conflicts seem to exist in the package file listings at the current
moment).


I just tried downgrading cygwin1.dll to the 2016-12-14 snapshot, emacs 
to 25.1-1 (released 2016-09-17), and coreutils to 8.26-1 (released 
2016-12-16).  The problem is still there with that configuration.  And 
starting with an off-white background is not necessary.  Even with no 
.minttrc, 'emacs-nox -Q' followed by 'M-x set-background-color RET white 
RET' turns the background gray.  I can also reproduce the problem in 
xterm, so I don't think Mintty is the culprit.


What about ncurses?  That was updated on 2017-01-27?  I haven't tried 
downgrading it yet, but I can probably try it later today.


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



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 few days before I get to this.

It may be possible that the coreutils update messed up things in a way
that I don't understand, but that's unlikely.  Or vim might have
delivered a file that conflicts with something from Emacs, but Emacs has
since been updated again and so that conflict would have flipped in
favor of Emacs at those times, which I didn't observe (and no such
conflicts seem to exist in the package file listings at the current
moment).


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