The lastest cmd2 cannot recognize ctrl key in fish shell

[KelvinChung2000]

This is using 53a5c0f which is the HEAD of main.

I am using fish shell, and this is in the vscode terminal

the tab is not woring.

But if I use bash, this is fine

[tleonhardt]

@KelvinChung2000 Thanks for reporting this issue Kelvin!

If you have any insight regarding how to fix it, please feel free to submit a PR. If not, we'll install fish and see what we can figure out. I've personally never used fish since I've been very happy with OhMyZsh.

P.S. Please tell me your parents are geeks and named you after the temperature scale ;-)

[KelvinChung2000]

I will have a look when I have time, as I am not supposed to get sidetracked this much and should be working on my thesis.

I picked this English name myself. The original intention is just a simple English name. However, this, by accident, made me into an "absolute unit".

[tleonhardt]

@KelvinChung2000 I have been unable to reproduce this on my end. I need some more information from you to help reproduce. Things like the following may all be helpful:

• What key(s) other than ctrl are you pressing?
• What version of fish are you running?
• What OS are you on?
• Does it work in fish if you are running in a normal terminal other than within the VSCode terminal?

I tried on a default install of fish from apt on a Debian 12 Linux VM running inside VSCode and could not reproduce the problem (this was with fish version 3.6.0).

[KelvinChung2000]

The keys I were trying are tabs and backspace.

• I am on fish 4.5.0
• I got another computer, and that device is running fish 3.7.1, which is working in the vscode terminal.
• I am using PopOs 22.04, which is basically Ubuntu.
• It is working fine in a normal terminal (kitty) with fish 4.5.

So this is likely only fish 4.x with the VSCode terminal combo?

[tleonhardt]

I also tested with fish 4.5.0 on macOS and everything worked fine in a normal iterm2 terminal.

Then I changed from a zsh shell in the VSCode terminal to fish and there was an issue with fish shell in the VSCode terminal in this case. zsh or bash work fine in the VSCode terminal.

However, then I closed VSCode, started fish in the terminal and relaunched VSCode from scratch from the terminal and switched to fish shell in VSCode terminal and everything worked fine.

So whatever is going on is subtle and is likely only happens with fish 4.x in a VSCode terminal. That is definitely outside the scope of something cmd2 can fix. So I am going to close this issue. If you find some really smart simple workaround we can apply in cmd2 to prevent this undesirable behavior, we would likely be open to adding something to help. Feel free to re-open the issue if you come up with something along those lines.

[tleonhardt]

Closing since this does not appear to be a cmd2 issue but instead some subtle problem with using fish 4.x inside a VSCode terminal.