Replies: 1 comment 4 replies
-
Who are you?
This is essentially controlled by your shell. I don't understand what you are asking. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using the same default shell configuration that was previously discovered by now a ghost account:
C:\msys64\msys2_shell.cmd-clang64 -defterm -here -no-startThe shell will always start in the current directory. This means the ecode directory (contains
ecode.exe) if I useecode -t, or the project's directory if I have opened a folder. It applies to all terminals, including the status bar terminal.I would love to have a way to improve the configuration, but I'm not skilled enough with Batch scripting to go any further when reading
msys2_shell.cmd. Copilot couldn't help me either, as it suggested solutions that didn't work. I'm mostly okay with this. It’s a bit annoying, but I consider it acceptable as long as I have my familiar MSYS2 CLANG64 environment.The problem that bothers me most is the name of the terminal tab, which is currently always set to the path of the current directory. As a result, I end up with a very long and uninformative tab name that is basically just the path to the current directory.
Beta Was this translation helpful? Give feedback.
All reactions