public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: chrstfer <chrstfer@protonmail.com>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: (No Subject)
Date: Fri, 24 Feb 2023 13:58:50 +1100	[thread overview]
Message-ID: <f8fc8d97-7b57-7012-e831-26b56239510a@cs.umass.edu> (raw)
In-Reply-To: <7A07r2fCCPwKcS2yk7WekLqq88LeTT0or1g3cOwDu8k7PLtEkNNb6WBaUtMSvs3dZL9udR-_fhCu6lnEZx4hq_OVFpGcrjSSPzT2JaYIdSs=@protonmail.com>

On 2/24/2023 1:51 PM, chrstfer via Cygwin wrote:
> Hi all,
> 
> First mail, so while I'm fairly sure it's on topic please forgive me if it isn't.
> 
> Has anyone tried to get a docker container with an X app in it to connect to the cygwin x server?
> 
> When I run startxwin after starting the wslg container the cygwin Xserver comes in at address (word?) :1 rather than :0, so the two servers can recognize each other (at least to some degree). I can run a cygwin X app in a cygwin console and get an X window, and I can run a wslg app in a wsl bash instance and get an X window, each on their respective servers. But when I set the env DISPLAY in one to the X of the other, it breaks.
> 
> This isn't just a stupid ask for a redundant use-case, either. The cygwin X server is vastly superior to the wslg one, at least insofar as integration with the windows 10 chrome; cygwin X windows no matter the library will snap like a regular windows window will. Anything coming out of wslg, at least when it comes to gtk3 (emacs-git) and QT4 (qutebrowser), have no native window decorations and don't snap. I've also been unable to find a way to run a docker container as a single X root window (ie to run a DE inside of a container) but I bet if I could connect to the cygwin X server that'd be fairly straightforward.
> 
> I'll be the first to admit I don't know too much about X so is what I'm asking even possible? (I do mainly use linux, but normally X is one of those things that i dont fiddle with much)
> 
> UItimately/mostly I'm just fed up of being stuck in Windows windowland at work and not having emacs-git*. At least thats how i landed on this topic, but it seems to me being able to run a docker container and have it hook into a cygwin X server that's already running would be a good feature generally. Especially if it would enable me to disable WSL again.
> 
> (*As an aside: while I have gotten it to compile, and it runs in the console, so many tests break that I'm afraid to even try compiling it for gtk3; so a docker container of debian stable seemed a logical next step and i half-expected it to just work, to be honest, given how seamless the rest of my cygwin experience has been recently, and I would put money on these two issues being on docker/docker-desktop/wsl, given how poor wslg's integration is despite being a microsoft project)

If it's of any help in understanding this, in wsl I set DISPLAY=:0
and can start X apps that connect to the Cygwin X server.  I wonder
if there are issues trying to run two X servers at the same time ...

Best - Eliot Moss

  reply	other threads:[~2023-02-24  2:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  2:51 chrstfer
2023-02-24  2:58 ` Eliot Moss [this message]
2023-02-24  3:07   ` chrstfer
2023-02-24  3:11     ` Eliot Moss
     [not found] <3E3A630C.9080803@yahoo.com>
2003-01-31 15:19 ` (no subject) Earnie Boyd
  -- strict thread matches above, loose matches on Subject: below --
2002-06-10  2:21 <no subject> Thomas Mellman
1999-02-24  2:15 (no subject) Celso Labinaz
1999-02-28 23:02 ` Celso Labinaz
1998-11-19 22:52 Sch5750
1997-05-22 19:25 Neal Feller
1997-05-05 16:05 Christoph Rippel

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=f8fc8d97-7b57-7012-e831-26b56239510a@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=chrstfer@protonmail.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).