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
I recently switched to using the fish shell and now I see screen corruption in vim after saving a Python file.
When the khuno background job completes fish outputs:
Job 1, “flake8 /tmp/vT0ZrIZ/0.py > /tmp…” has ended
The workaround is set shell="/bin/bash" at the top of my .vimrc
set shell="/bin/bash"
The text was updated successfully, but these errors were encountered:
This is far from ideal, but it looks like it is the shell just persisting that message even without vim in the mix:
~> ls > /dev/null & 'ls > /dev/null &' has ended
I am going to try and see if there is any way to mitigate that. The workaround is OK for now, but that is going to be really annoying for users
Sorry, something went wrong.
alfredodeza
No branches or pull requests
I recently switched to using the fish shell and now I see screen corruption in vim after saving a Python file.
When the khuno background job completes fish outputs:
Job 1, “flake8 /tmp/vT0ZrIZ/0.py > /tmp…” has ended
The workaround is
set shell="/bin/bash"
at the top of my .vimrcThe text was updated successfully, but these errors were encountered: