Repository navigation
feat: customizable command via LAUNCH_EDITOR env - #49
Merged
Merged
Conversation
Author
|
Please see the discussion in #39 too |
ghost
mentioned this pull request
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
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.
slightly different implementation than #39
The code changes are minimal, basically the LAUNCH_EDITOR value is used as first guess, bypassing scanning the process list.
In addition, it preserves
getArgumentsForPositionsupport, so that users can use it to either force a specific supported editor viaLAUNCH_EDITOR=codiumor go full custom viaLAUNCH_EDITOR=custom-script.sh