Watch: spaces in command are not preserved
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
Research direction
Start by locating the Watch command entry point and how it constructs the command passed back to rc. Reproduce the printf example from the issue, then verify that arguments containing whitespace remain single arguments and that the displayed output matches a direct rc invocation.
Written by the indexing model from the issue text.
Description
When invoking Watch with arguments which contain spaces, the arguments are not preserved. For example, this command works as expected in an rc session:
% printf '%s %s %s\n' 1 2 3
1 2 3
But when run through Watch:
Watch printf '%s %s %s\n' 1 2 3
We would expect the argument parsing rc does when invoking Watch to be preserved, however the first string is split again:
To avoid this, Watch will need to quote any arguments with whitespace so that they are parsed correctly by rc again.
- Dominant language
- Go
- Stars
- 377
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from 9fans/go
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
samterm doesn't compile on AIXPossibly taken @bhuntsman claimed this 636 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Containerpak/cpak#93 ·
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug laptop
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
router-for-me/CLIProxyAPI#7607 ·
Maintainers usually reply within 1 day
-
enhancement ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
myNameArnav/lex#52 ·
Maintainers usually reply within 1 day