You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For commands like kubectl that aren't natively supported by Warp, the tab completion should defer to the shell completion.
When running in a normal terminal emulator running something like kubectl <tab> will give a list of supported operations and even stuff like kubectl describe pod <tab> will show a list of pods.
With Warp this doesn't happen and instead, it just shows a list of files in the working directory. This is super annoying and makes it very hard to use. I find myself having to switch between 2 terminals because of this.
I've also noticed this happen with other commands like Skaffold. I think it would be unreasonable to expect native support for every command, but having a way to fall back to Shell completion would be nice.
To Reproduce
Steps to reproduce:
Go to '...'
Click on '...'
Scroll down to '...'
See error '...'
Expected behaviour
No response
Screenshots
No response
Operating System
MacOS
OS Version
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
For commands like
kubectl
that aren't natively supported by Warp, the tab completion should defer to the shell completion.When running in a normal terminal emulator running something like
kubectl <tab>
will give a list of supported operations and even stuff likekubectl describe pod <tab>
will show a list of pods.With Warp this doesn't happen and instead, it just shows a list of files in the working directory. This is super annoying and makes it very hard to use. I find myself having to switch between 2 terminals because of this.
I've also noticed this happen with other commands like
Skaffold
. I think it would be unreasonable to expect native support for every command, but having a way to fall back to Shell completion would be nice.To Reproduce
Steps to reproduce:
Expected behaviour
No response
Screenshots
No response
Operating System
MacOS
OS Version
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: