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
add environment variable like TERM=xterm #360
Comments
As discussed in #356, the environment variable is required to work around a bug in mono which has already been fixed so should be available soon - mono/mono#6752. So I don't think it makes sense to update OmniSharp-vim to deal with this temporary issue. Edit 2018-05-02: Don't try this, doesn't work As a stop-gap until the updated mono becomes available, you could patch your OmniSharp-vim by adding the following line to
|
thank you for fast help as usual. i was sick a week ago so i couldn't reply |
I don't really know what you mean? Are they omnisharp errors? In any case, if the above workaround works for you, then yes, close this issue and open a new one for unrelated problems. |
Yes you're right, that workaround I described above doesn't work, sorry. |
it's okay. your fast response already helped me giving interest in this. |
@nickspoons, and what if the command variable is assigned in this way? |
The referenced mono bug has been fixed and backported, so I'm closing this issue. |
according to issue #356 i would need an environment variable of TERM=xterm in order to start the omnisharp server.
so is there anyway to add those environment variable so i could successfully launch ominsharp server every time i launch vim for .cs file ?
The text was updated successfully, but these errors were encountered: