From: Fergus Daly <fergusd84@outlook.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Cc: Fergus Daly <fergusd84@outlook.com>
Subject: wish8.6 perfect in Cygwin32, misbehaves in Cygwin64
Date: Wed, 2 Sep 2020 20:46:18 +0000 [thread overview]
Message-ID: <DB6PR03MB3013A4FAA09454286C994C02A42F0@DB6PR03MB3013.eurprd03.prod.outlook.com> (raw)
Can't entirely recall* when wish8.4 was versioned up to the current wish8.6 in Cygwin,
or whether there was an intermediate wish8.5 - I think it must be nearly a decade ago, or possibly
longer - but I do remember that
1. wish8.4 "worked" in bash and rxvt terminals (I think all this preceded mintty) AND also in xterm
2. wish8.[56] "fails" in bash and mintty terminals and insists on DISPLAY being set, i.e. requires XWin
(by which I mean wish was the driver for Tcl/Tk menus, windows, other displays).
Actually I hung on to the components that comprise wish8.4 and toggle between them at will and can
confirm the truth of (1) and (2) above.
Generally though, I guess users have upgraded to wish8.6 long since and if they use it to provide Tcl/Tk
menus (?) or sidebar Help Tcl/Tk windows (?) are used to requiring e.g. xterm in XWin in order to do so.
ALL THIS in Cygwin-32.
Recent unconnected threads in this list have persuaded me to trial Cygwin-64 (and, if happy, I'll jettison the
Cygwin-32 platform). I have installed it identically (see setup -P below).
The many contexts in which wish8.6 has worked properly in Cygwin-32 are, for me, failing uniformly in
Cygwin-64. By this I mean, Tcl/Tk menus are mutely failing to appear, Tcl/Tk Help windows are mutely failing
to appear.
Can't think what I'm getting wrong. But a good first step would be: have any of you, in advancing from Cygwin-32
to what was intended to provide identical functionality in Cygwin-64, experienced similar unexplained glitches,
and managed to solve them? Or is this experience unique? If you can help with this specific Tcl/Tk problem, that
would be perfect!
BTW I use
setup-x86[_64] -P ..,..,tcl-tix,tcl-tk-devel,..,..
to build the supporting platforms.
Thank you!
* "Can't entirely recall .. .." (line 1):
Typing "site:cygwin.com searchstring" into the Google search bar used to yield pages of output, including hits for
very specific strings e.g. "site:cygwin.com fergus grap" to remind myself what I asked about grap as long ago as
2001 - and, much more helpfully, what somebody kindly answered. Now, after a measly trickle of hits, Google
explains the paucity with a reference to data protection. I know I asked specifically about the loss of versatility
with wish8.4 at the time, but cannot find the thread.
Is there a vehicle which still permits an exhaustive search of the entire Cygwin project mailing archive?
next reply other threads:[~2020-09-02 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 20:46 Fergus Daly [this message]
2020-09-02 21:17 ` Marco Atzeri
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=DB6PR03MB3013A4FAA09454286C994C02A42F0@DB6PR03MB3013.eurprd03.prod.outlook.com \
--to=fergusd84@outlook.com \
--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).