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
&shell suddenly set to sh instead of bash? #2845
Comments
Strange. I believe this is relevant: vimtex/autoload/vimtex/jobs/vim.vim Lines 152 to 185 in 8dad59a
But it's hard to consider this without being able to reproduce any problems... |
Anyway the reason why I suspect that is because the time I see that happen, I run Is there any possibility the function can be called "asynchronously"? (i.e. is there some threading in vimscript?) Because if it's possible, it's certainly possible for two interleaving calls of the function to incorrectly restore the values:
then the original value (bash) is lost. Edit: looks like there's a few calls of Edit2: With some testing, looks like the call to
so I'm not sure if it's possible to trigger a race condition this way. Too bad I don't write down exactly which line causes the problem in the function, but if I recalled correctly it's the latter restoration line (i.e. |
No, I don't think there is. Vimscript does not allow asynchronous stuff.
Good question. It may be possible, but it would be very unlikely! |
Description
While using vimtex, I notice once that &shell is suddenly set to sh. My default setting is bash.
Steps to reproduce
Currently not reproducible, but I suspect it's some sort of race condition in
autoload/vimtex/jobs/vim.vim → vim_unix_run -- maybe if two files attempt to call the function independently, it will break...?
VimtexInfo
Custom fork, actually. Might not be latest version, and I haven't tried reproducing it in latest version.
The text was updated successfully, but these errors were encountered: