We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For the sake of completeness, I flagged this issue to WT people: #3367. maybe you could be interested.
The text was updated successfully, but these errors were encountered:
Where the TERM variable is set in MSYS2? The issue seems related to this variable.
TERM
When one starts MSYS2 with the launcher msys2.exe, TERM results equal to xterm. In WT it is set to cygwin.
msys2.exe
xterm
cygwin
Now if I use in the WT profile
"commandline": "cmd.exe /c \"set TERM=xterm&& set MSYSTEM=MSYS&& set MSYS=winsymlinks:nativestrict&& C:/msys64/usr/bin/bash.exe --login\""
the issue seems fixed but Emacs in terminal (msys/emacs 26.3-1) has issues: its window displays garbage and the colors are not so good.
msys/emacs 26.3-1
Sorry, something went wrong.
No branches or pull requests
For the sake of completeness, I flagged this issue to WT people: #3367. maybe you could be interested.
The text was updated successfully, but these errors were encountered: