We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
b
Fish: version 3.7.1-1593-g5b324f8ec OS: Arch Linux Term: Kitty
Yes, this does happen without third-party customizations.
b is misbehaving, at least with regards to slashes (where I noticed it). Example:
content:
cd /usr/bin/zsh[CURSOR] # in normal mode, press b cd /usr/bin/[z]sh # (correct) # press b again cd /usr/[b]in/zsh # (incorrect)
Compare this to real vim or neovim;
cd /usr/bin/zsh[CURSOR] # in normal mode, press b cd /usr/bin/[z]sh # (correct) # press b again cd /usr/bin[/]zsh # press b again cd /usr/[b]in/zsh
More clearly, just enter vi mode, press b from the end of the line and compare to vim to see the difference.
Zsh vi mode seems to handle this case fine.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Fish: version 3.7.1-1593-g5b324f8ec
OS: Arch Linux
Term: Kitty
Yes, this does happen without third-party customizations.
b
is misbehaving, at least with regards to slashes (where I noticed it). Example:content:
Compare this to real vim or neovim;
More clearly, just enter vi mode, press b from the end of the line and compare to vim to see the difference.
Zsh vi mode seems to handle this case fine.
The text was updated successfully, but these errors were encountered: