run synchronously on process load, and restart extension host on change #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#12 made me think, it seems like the only way to guarantee direnv is setup before other extensions is to do it both synchronously (no promises in the initialization code) and at process startup (otherwise it depends on extension activation order).
When reloading, it actually causes the extension host to restart because again, that seems like the only reliable way to ensure the new env is applied.
Which makes for a pretty badly behaved extension in some ways (it takes effect even if it's deactivated), but I don't see much alternative if we want to guarantee it happens first.