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
The file paths outputted by git status, when there is a space in the path, are not valid. They contain an extra layer of quotes.
Steps to reproduce
touch "a b.txt"
select "a b.txt" in search git status
notice the output is '"a b.txt"', and if you try to cat it you'll get cat: "a b.txt": No such file or directory
Comments
Looking for contributors to fix this one! @kidonng if you're interested 😉
The test tests/search_git_status/outputs_right_paths.fish will also need to be updated. It attempts to test paths with spaces but it's not catching the bug :(
The text was updated successfully, but these errors were encountered:
PatrickF1
changed the title
search git status adds too many layers of quotes to paths with spaces
search git search status doesn’t work for files with spaces
Feb 5, 2022
This fixes a bug where file paths outputted by search git status include an extra layer of single quotes if the path includes a space. Turns out this is because we string escape all our paths before writing them to the command line but git status already string escapes paths with spaces.
Fixes#220
Describe the bug
The file paths outputted by git status, when there is a space in the path, are not valid. They contain an extra layer of quotes.
Steps to reproduce
touch "a b.txt"
select "a b.txt" in search git status
notice the output is
'"a b.txt"'
, and if you try to cat it you'll getcat: "a b.txt": No such file or directory
Comments
Looking for contributors to fix this one! @kidonng if you're interested 😉
The test
tests/search_git_status/outputs_right_paths.fish
will also need to be updated. It attempts to test paths with spaces but it's not catching the bug :(The text was updated successfully, but these errors were encountered: