fix: properly parse fzf entries with git status indicator #64
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
… parsing The status menu content was using gf_git_command_with_header which forces color.ui=always, embedding ANSI color codes in the output. When the status interpreter tried to extract file paths with cut -c4-, it was cutting through the middle of these invisible escape sequences, causing Alt-E to attempt editing files with status codes (like "M ") still in the path. Fixed by using color.status=false when generating the status menu content, ensuring clean output that can be correctly parsed by cut -c4-.
Contributor
Author
|
This isn't working properly. Will report back when I've had more time to tinker with it unless there is an easier way. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I'm not sure if this actually works yet, but copy/edit/etc don't work when there is a status indicator on the file (
??,M, etc)Will test and revise, unless I'm doing something wrong to trigger this in the first place.