-
Notifications
You must be signed in to change notification settings - Fork 12
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
direnv.path.executable only works with full path #754
Comments
Sadly vscode doesn't support that, see microsoft/vscode#2809
Weird, that should work, that's even the default value. Can you explain this one in a bit more detail? |
Not much to explain, it says it didnt found the executable, through the popup on the right bottom in vscode. Only time it doesnt, is with the full path. |
Does the same error occur when you reset the setting to the default value? |
Could be because I am using nushell as default shell, there it is set. It is also the default shell in vscode, but might not matter if internals are tied to bash. |
Yeah, confirmed, it's because |
FWIW that's done by your windowing system (or whatever context you start vscode in), vscode doesn't (and cannot) care about your shell. |
Hm, most context are by going through to the folder and typing Not sure where else the default could be changed, I already had changed in They dont seem to matter. |
I get the same error using the absolute path to direnv, I copy-pasted the output of Setting it to just |
Solution is what they recommend at direnv, you have to set the eval in the |
Hi,
I was trying out the extension, but it seems that it is only able to recognize direnv through the full path.
/home/user/.../direnv
I tried with bash env var
$HOME/user/...
and it didnt workI tried with nushell env var
$env.HOME/...
and it didnt workand tried with tilde
~/.../direnv
and it didnt work.That does not make the path very flexible in the config, is there a way to make it work with variables or tilde?
Oh, and straight call to
direnv
does not work.The text was updated successfully, but these errors were encountered: