From: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>
To: cygwin@cygwin.com
Subject: Cygwin/X - doorknock like behaviour for new windows
Date: Fri, 20 Oct 2023 11:50:55 +1100 [thread overview]
Message-ID: <a22bf269-ad22-4bdc-814f-bf5594e845e8@shaddybaddah.name> (raw)
Hi,
I've now noticed this across two different installations, both Windows
10 and Windows 11. I've refrained from attaching a cygcheck output for
the moment, because I'm confident this is reproducible.
What I am seeing is that for Cygwin/X, in multi-window mode (and it
just occurred to me it would be helpful to check the behaviour in
rooted(? manual page terminology) mode. I'll follow-up on this)...
in multi-window mode (Xwin -multiwindow), when I try to open an X window
for any given app, it is not displayed on the first run.
Either nothing happens, and I must ctrl-c the command line and retry, or
a non-visible Window is created, so that the icon tray displays an icon
with the generic X image, but not the icon of the X app itself.
What I understand to be the base control test is to use xbiff. So just
for completeness, this is how I reproduce for xbiff:
terminal 1
===
$ /usr/bin/XWin :1 -nolisten tcp -ac -multiwindow
terminal 2
===
$ DISPLAY=:1; export DISPLAY
$ xbiff
Warning: Cannot convert string "flagup" to type Pixmap
Warning: Cannot convert string "flagdown" to type Pixmap
^C
$ xbiff
Warning: Cannot convert string "flagup" to type Pixmap
Warning: Cannot convert string "flagdown" to type Pixmap
<xbiff displays>
I'll follow-up with my rooted mode observations.
--
Regards,
Shaddy
next reply other threads:[~2023-10-20 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 0:50 Shaddy Baddah [this message]
2023-10-20 1:40 ` Shaddy Baddah
2023-10-21 8:24 ` Cygwin/X - *bizarre discovery* " Shaddy Baddah
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=a22bf269-ad22-4bdc-814f-bf5594e845e8@shaddybaddah.name \
--to=lithium-cygwin@shaddybaddah.name \
--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).