Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

auto-completion of bash shell commands are not working #743

Open
simonepittis opened this issue May 26, 2024 · 5 comments
Open

auto-completion of bash shell commands are not working #743

simonepittis opened this issue May 26, 2024 · 5 comments
Labels
stale There has not been activity on this issue or PR for quite some time.

Comments

@simonepittis
Copy link

auto-completion of bash shell commands are not working on v18.0.0

auto-completion command with TAB work on 17.3.0

@bakerkj
Copy link

bakerkj commented May 26, 2024

I can confirm I am seeing a related problem in that my .bash_profile is no longer running in 18.0.0.

I suspect the default shell is different between 17.3.0 and 18.0.0.

Having a configuration option to select bash, zsh, etc might be a reasonable path forward.

@NodeJSmith
Copy link

Same issue here on version 18.0.0, it seems that I get dropped in a sh shell instead of a zsh shell. Everything works normal if I run zsh to get into a proper zsh shell. Not sure what happened in the latest update

@aodtcr
Copy link

aodtcr commented May 27, 2024

Same here- autocompletion, as well as other commands and aliases are not working. It seems the default ash shell is loaded instead of zsh, although zsh is installed and works when its run manually (as mentioned by @NodeJSmith).
Somehow zsh is not started when a new terminal session is opened.
Restarting the addon, or uninstalling and reinstalling the addon, does not solve the issue for me. Going back to v17.3.0 does run zsh as default shell.

@VlastiBroucek
Copy link

Same issue for me - unfortunately, I've created #744 (comment) before reading this one as the title did not suggest similarity.

Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale There has not been activity on this issue or PR for quite some time.
Projects
None yet
Development

No branches or pull requests

5 participants