X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 37F9F385B530 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1677207128; bh=yivkM6r6lH3a8t8shmrzMwzBpxufTP/8+foA3JmPLHs=; h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=F3iTjGcbTWEsLJggjT19MuJEU0GJTMS2qNLUfbGqbDxMnNNqvzhSnXxSJ77z6v7dj AiiTMG8794B61vmyfH3ZWGY/GPb1U2HA66NTJEUWhoDfyPucL2csLzLC2PC4mT71OK JrbM9aZKdfYb9BTznad38mtYt+NgWMgMB/SpRF0I= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 05653385842B Date: Fri, 24 Feb 2023 02:51:39 +0000 To: "cygwin AT cygwin DOT com" Subject: (No Subject) Message-ID: <7A07r2fCCPwKcS2yk7WekLqq88LeTT0or1g3cOwDu8k7PLtEkNNb6WBaUtMSvs3dZL9udR-_fhCu6lnEZx4hq_OVFpGcrjSSPzT2JaYIdSs=@protonmail.com> Feedback-ID: 21821362:user:proton MIME-Version: 1.0 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_MSPIKE_H2, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: chrstfer via Cygwin Reply-To: chrstfer Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Cygwin" 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) Chris B -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple