DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4B5F1IRv3302143
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 67EB53858D20
Message-ID: <de42398d-370c-46f8-b2a8-536e0a4a283a@kircheis.it>
Date: Thu, 5 Dec 2024 16:00:36 +0100
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Conflict between tmux and cygwin
From: Federico Kircheis via Cygwin <cygwin@cygwin.com>
Reply-To: Federico Kircheis <federico@kircheis.it>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>

It seems there is a conflict betwene some tmux functionalities and cygwin.


In tmux it is possible to open a new windows with "tmux new-window -c 
$NEW_WD", the new shell should be located at "$NEW_WD", but it seems not 
to work with cygwin; th new shell is always openeed at ~


I thought I had it working years ago, and assumed it was a tmux specific 
bug on cygwin, as tmux on Linux work as expected, thus I hacked around 
the issue by making aliases and adding cd commands.

Today I found https://github.com/tmux/tmux/issues/3283, and I can 
confirm that the CHERE_INVOKING functionality is causing the issue.

I would like to avoid to change the provided /etc/profile to avoid 
conflicts during upgrades, but I would also like to have tmux work 
correctly out-of-the-box, like on all other platforms.

Is there some way to reach such status?

Best

Federico


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