-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commands are echoed without quotation marks in the log #169
Labels
enhancement
New feature or request
Comments
hi @dbohdan, thanks for the feedback. I think your suggestion makes sense, I'll try get it into the next release. |
nat-n
added a commit
that referenced
this issue
Sep 30, 2023
nat-n
added a commit
that referenced
this issue
Sep 30, 2023
nat-n
added a commit
that referenced
this issue
Sep 30, 2023
nat-n
added a commit
that referenced
this issue
Sep 30, 2023
nat-n
added a commit
that referenced
this issue
Sep 30, 2023
nat-n
added a commit
that referenced
this issue
Sep 30, 2023
nat-n
added a commit
that referenced
this issue
Sep 30, 2023
nat-n
added a commit
that referenced
this issue
Sep 30, 2023
This enhancement is now available in v0.24.0 🚀 |
That was quick! Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you define a command task with parts in quotes, the command shows in the log without the quotes. This makes it harder to understand the log and also prevents you from copying and pasting the command into your shell.
For example, for the task
the output from Poe the Poet 0.23.0 is
But as a user, I expect output like
I don't think the quotation marks must necessarily be those in the literal text. What I have done in similar situations is join the command with
shlex.join
before logging it.The text was updated successfully, but these errors were encountered: