Handle alternate linux config directory paths for addons #2892
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.
Microsoft's build of VSCode uses
~/.config/Code
on Linux. Popular alternate builds VSCodium and Code - OSS use different names for their config directories. And if a distro or user compiles with an uncommon name, it could be arbitrary.This patch checks the three named variations, then all config dirs, then produces an error.
I also had it memoize the addons path rather than search for it 3+ times during startup (once for every instance of
${addons}
)This fixes the problem I ran into in LuaLS/LLS-Addons#182