Support for multiple local terminals on Windows

[dmorris68]

I'm loving Wave but am somewhat of a terminal power user who has setup multiple terminal profiles (shells) in Windows Terminal and uses them heavily. My understanding is that, by default, Wave on Windows will always launch Windows Terminal's default shell. If my default shell is setup as Powershell, then that's the only local (non-WSL or non-SSH) terminal I get. If I want a Command Prompt using CMD.EXE then I have to first change my default Windows Terminal profile to that.

Unless I'm overlooking it, I'd like to see support for multiple Windows Terminal profiles and/or multiple term:localshellpath options, just like you can have multiple WSL or SSH connections.

I understand that I can set term:localshellpath to override the default behavior and run that particular shell, but again that's forcing a single terminal type. I'd have to change that again and relaunch Wave to access another terminal type, or else run it from the default shell which results in a nested shell. That just seems inefficient.

This is very limiting. Depending on what I'm doing, I might want to run Powershell, CMD, bash, or something else as my local terminal shell, and sometimes multiple at once. The window management features of Wave would make running multiple shells really convenient.

I can create a feature enhancement ticket but wanted to start the discussion here first to get feedback or ideas I may have overlooked.

[dmorris68]

Ok, so disregard the Windows Terminal assumptions. Turns out I was operating on bad info. Somewhere I read that Wave was using Windows Terminal for it's local Windows shell. It is not, apparently. I've looked around in the code to see how the local shell is being launched, and it looks like Wave is executing local shells directly, with built-in support for running bash, zsh, fish, or pwsh. And its default Windows local shell is pwsh (PowerShell). Anything else requires an override with term:localshellpath but again that just gives you a single shell option.

Ideally you could have multiple local shell profiles, like Windows Terminal allows.

I really like Wave and it has a lot of potential, but this shortcoming will likely have me sticking with Windows Terminal more often just for this flexibility.