DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4B72o1W64052820
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 29CDE3858410
MIME-Version: 1.0
Date: Fri, 6 Dec 2024 18:48:50 -0800
Message-ID: <CAAHpriMb0cYqx+zyByV2_1Zkfpj5zX3JSaAmWk4o8AMcFuAcwA@mail.gmail.com>
Subject: Re: Conflict between tmux and cygwin
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
From: Keith Thompson via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Keith Thompson <Keith DOT S DOT Thompson AT gmail DOT com>
Cc: Keith Thompson <Keith DOT S DOT Thompson AT gmail DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

It's not really a tmux issue. You can demonstrate it just by invoking
a shell.

For example, if you "cd /tmp" and then invoke a new shell with
"bash -l", the code in /etc/profile will cd to your home directory.
(This doesn't happen on Ubuntu, for example, which has a
different /etc/profile.)

But if you invoke bash without "-l", or with "CHERE_INVOKING=1 bash
-l", the new shell will have /tmp as its current directory.

"chere" is a script, installable via Cygwin setup, that enables
opening a Cygwin terminal in a specific directory via the Windows
Explorer context menu (right-click). I haven't tried it myself yet.

Here's the relevant code from /etc/profile :

# Make sure we start in home unless invoked by CHERE
if [ ! -z "${CHERE_INVOKING}" ]; then
  unset CHERE_INVOKING
else
  cd "${HOME}" || echo "WARNING: Failed attempt to cd into ${HOME}!"
fi

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