-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Doesn't work when using SHELL=/bin/tcsh #159
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
Comments
Thanks for the report. Could you test if the above patch fixes your problem? https://raw.githubusercontent.com/junegunn/vim-plug/fix-159/plug.vim |
Thanks :-) I tried all the commands, and everything seems to work fine. A related issue (minor) I noticed: If I use As far as I can see, there's no |
Good point, thanks! |
Fix #159 - Avoid errors on tcsh and fish
The fixes are now merged to master. Thanks. |
I'd like to reopen this issue. The implemented fix is not correct because
So, if vim is started in a tcsh the shell redirection used in
|
@vhda I see, but does it make vim-plug fail? I tried with |
I detected the issue exactly because I was trying to call |
@junegunn forgot one very important detail: I use dash in Debian. As such, when vim-plug sets |
@vhda I can't replicate either. Seems to work fine. Don't think last detail matters. Ubuntu also has To test, all I did was invoke tcsh then start vim & PlugUpdate. You are saying this procedure should fail? Side Note: When you say you use dash, you mean as your terminal for daily commands right? I'm curious, why? |
No, I use tcsh as my command shell. dash is only used as the default shell of the system. I am also unable to replicate this in my Debian unstable at home, so I'll need to debug this further at work tomorrow. Will add more information as soon as I have any. |
I've been using vim-plug with tcsh as my login shell since the issue was fixed in February; haven't experienced any problems with either I believe vim-plug tries to use Ruby, Python, or a VimScript fallback depending on which features are available. My Vim has both +ruby and +python, so perhaps this problem only occurs when using Python or the VimScript fallback? |
@vhda Well, it's strange, but anyway, the following patch will set shellredir as you initially suggested. Does it help? |
@junegunn your patch fixes the problem. Debug information: my vim installation has +ruby, +python and -python3. My default shell is tcsh and /bin/sh points to dash (version 0.5.7-4+b1). Using :PlugUpgrade to understand that two temporary files are created:
The error I have is in the second temporary file and the error message is the following:
I still was not able to find any culprit other than |
@vhda Okay, I was able to reproduce the error on OS X by
And confirmed that changing |
@junegunn finally! I was starting to believe I had something wrong on my system! :) |
This is, presumably, the same issue as with the
fish
shell: #12 , some people also reported problems withzsh
as well...IMHO, the proposed workaround is not a very good one. If I use
set shell=/bin/sh
in my vimrc, all my:!cmd
filters now use/bin/sh
instead oftcsh
; so I lose thetcsh
semantics I'm used to, including my aliases that I use intcsh
. I could set this manually before every vim-plug command (which is what I do now), but this is obviously rather awkward.Can't vim-plug set the shell to
/bin/sh
when running shell commands (and re-set it to whatever it was) on completion? Or use some other method that doesn't require globally setting the shell in Vim (such as maybesystem('/bin/sh -c cmd')
...Thanks :-)
The text was updated successfully, but these errors were encountered: