Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSYS2 environment $HOME is incorrectly pointed to /c/Users/<UserID> #6079

Closed
lbmeng opened this issue Apr 2, 2022 · 4 comments
Closed

MSYS2 environment $HOME is incorrectly pointed to /c/Users/<UserID> #6079

lbmeng opened this issue Apr 2, 2022 · 4 comments

Comments

@lbmeng
Copy link

lbmeng commented Apr 2, 2022

Describe the problem:
[A clear and concise description of what the bug is.]
MSYS2 environment $HOME is incorrectly pointed to /c/Users/<UserID>, but it should be pointed to /home/<UserID>

The native MSYS2 shell, as well as Windows terminal, maps $HOME correctly to /home/<UserID>.

Tried the latest tabby, the issue still exists.

To Reproduce:
[Steps to reproduce the behavior]

Install MSYS2 (https://www.msys2.org), and use tabby to open one of the MSYS2 supported configuration, for example, MSYS2 (MINGW64)

@lbmeng lbmeng added the T: Bug label Apr 2, 2022
@Eugeny
Copy link
Owner

Eugeny commented Apr 2, 2022

Don't you have to set up the MSYS2 starting directory manually in Windows Terminal?

@lbmeng
Copy link
Author

lbmeng commented Apr 2, 2022

Ah, thanks for the quick update!

It looks like I did follow the MSYS2 official guide to set up my Windows Terminal.

It seems there is no corresponding setting in tabby to configure MSYS2?

@Eugeny Eugeny closed this as completed in 94b3212 Apr 2, 2022
@lbmeng
Copy link
Author

lbmeng commented Apr 19, 2022

Reopening this issue, as it was only partially fixed in 1.0.175.

1.0.175 seems to only fix the starting directory so that it points to /home/<UserID>, but the $HOME environment variable still points to /c/Users/<UserID>

@lbmeng
Copy link
Author

lbmeng commented Apr 19, 2022

Oops, it looks like I don't have the privilege to reopen this issue. I will file a new issue then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants