Fix commands failing when current directory path contains spaces #67
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.
Commands were failing with "too many arguments" error when the current working directory's full path contained spaces. This happened because the
runmethod inCommandswas using simple string joining instead of proper shell escaping.The issue occurred in this line:
When a path like
/home/my work/repowas part of the command arguments, the shell would incorrectly parse it as multiple separate arguments instead of a single path.Before fix:
After fix:
The fix uses
Shellwords.shelljoin(cmd)which properly escapes spaces and other shell metacharacters, ensuring arguments are parsed correctly regardless of their content.Fixes #66.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.