fix: Resolve PATH environment issue in FuzzyGrep.runCommand #106
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.
In
FuzzyGrep.runCommand
, the test environment (e.g., runIde) applies the PATH variable normally, allowing tests to succeed without issues. However, in the actual built plugin, the PATH is limited to basic values such as /usr/bin, which means commands like rg (installed via Homebrew) are not recognized.To address this, the command execution method was changed from ProcessBuilder to GeneralCommandLine so that IntelliJ properly inherits the PATH environment as described here:
https://stackoverflow.com/questions/78851077/intellij-plugin-deficient-path-environment-variable
ProcessBuilder
toGeneralCommandLine
to ensure proper PATH inheritance in IntelliJ plugins.