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
It seems some hosting services mount /tmp without execute permissions which means search won't work since we extract and execute rg from there. We could try /tmp, the binary's directory, and then the system-installed rg if it exists in that order (possibly we'll want to ensure it's at least a certain version---I don't think VS Code makes any changes to ripgrep but we might want to double-check). If all fail we should output a message explaining that search won't work and how to fix it.
It might be better to use $XDG_CACHE_HOME or $HOME/.cache instead of /tmp. Golang stdlib does a pretty good job of finding cache dir so I guess you could just copy that
I have a dream that I can install this easily as 123 on all of my clients with their own jailed account + to avoid rebuilding it manually on each account... so all their extensions, config and stuff won't mix by others...
Activity
deansheather commentedon Oct 24, 2019
It might be better to use
$XDG_CACHE_HOMEor$HOME/.cacheinstead of/tmp. Golang stdlib does a pretty good job of finding cache dir so I guess you could just copy thatcode-asher commentedon Oct 24, 2019
Ahh good point, I like that.
Succubussix commentedon Oct 24, 2019
+1 for this.
I have a dream that I can install this easily as 123 on all of my clients with their own jailed account + to avoid rebuilding it manually on each account... so all their extensions, config and stuff won't mix by others...
nhooyr commentedon Jan 29, 2020
Related #1287
This should be fixed anyway by Asher.
Squashed 'lib/vscode/' changes from e5a624b..ea3859d
Squashed 'lib/vscode/' changes from e5a624b..ea3859d