You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As soon as I add the following snippet to my user settings.json, this direnv extension stops to properly expose environments to tasks of type shell as it previously did:
* Executing task: my-direnv-provided-exe
/run/current-system/sw/bin/bash: line 1: my-direnv-provided-exe: command not found
* The terminal process "/run/current-system/sw/bin/bash '-c', 'my-direnv-provided-exe'" failed to launch (exit code: 127).
* Terminal will be reused by tasks, press any key to close it.
Here's the expected behavior:
* Executing task: my-direnv-provided-exe
Hello from 'my-direnv-provided-exe'!
* Terminal will be reused by tasks, press any key to close it.
You can use an .envrc such as:
PATH="$PATH:$PWD/bin"
And a my-direnv-provided-exe script under a bin directory in your workspace:
#!/bin/shecho"Hello from 'my-direnv-provided-exe'!"
Don't forget to chmod a+x ./bin/my-direnv-provided-exe.
Note that in order to reproduce you might have to remove ~/.config/Code is order to reproduce as vscode seems to be persisting some cache of a task's environment. Don't forget to add the settings.json snippet again after removal.
The text was updated successfully, but these errors were encountered:
As soon as I add the following snippet to my user
settings.json
, this direnv extension stops to properly expose environments to tasks of typeshell
as it previously did:As soon as I comment out this setting, it starts to work again.
Here's a
tasks.json
file to reproduce:Here's the error I get:
Here's the expected behavior:
You can use an
.envrc
such as:PATH="$PATH:$PWD/bin"
And a
my-direnv-provided-exe
script under abin
directory in your workspace:Don't forget to
chmod a+x ./bin/my-direnv-provided-exe
.Note that in order to reproduce you might have to remove
~/.config/Code
is order to reproduce as vscode seems to be persisting some cache of a task's environment. Don't forget to add thesettings.json
snippet again after removal.The text was updated successfully, but these errors were encountered: