3 ms·
mintty, by far. I'm surprised no one has recommended it yet. The new Windows Terminal is just not ready. It's death by a thousand paper cuts. I keep an eye on
by 1996 7y ago
mintty, by far. I'm surprised no one has recommended it yet.
The new Windows Terminal is just not ready. It's death by a thousand paper cuts.
I keep an eye on it, but here's an example from right now when I start it with msys bash which otherwise works just fine:
bash: cut: command not found
dircolors: no SHELL environment variable, and no shell type option given
# echo $SHELL
/usr/bin/bash
# which cut
/usr/bin/cut
- mcswell 7y agoI'm confused. 'cut' works just fine for me in the Windows Terminal: ------- > echo $SHELL /bin/bash > echo "foo bar" | cut -f 1 -d ' ' foo ------ I'm using the WSL Ubuntu bash. Could your problem be with this 'msys' you're using? (I'm not sure what the 'dircolors' SHELL env var is--I haven't used 'dircolors', but 'man' tells me it's a program that sets the LS_COLORS env var, not an env var itself. And it says it has a shell type option, although that seems to be limited to C-shell and Bourne shell. Or maybe you mean dircolors doesn't pay attention to the SHELL env var? Again, that sounds more like a problem with the msys bash implementation, rather than the Windows Terminal.)