Conflict between tmux and cygwin

[Federico Kircheis]

On 7 December 2024 02:48:50 UTC, Keith Thompson <Keith.S.Thompson@gmail.com> wrote:
>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

Hi,

Yes, I wrote myself that it is not a tmux issue but a config in /etc/profile, as it is also written on the bug report.

The question was of it is possible to have tmux work correctly out of the box without having end users changing /etc/profile, and if this conflict in functionalities was known to packagers and mantainers