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
I've noticed that adding whitespace removes the last character of the command inputed.
e.g.
// Command ran is ngin instead of nginx
concurrently \"nginx \"
[0] /bin/sh: 1: ngin: not found
[1] exited with code 0
[0] ngin exited with code 127
Although it works perfectly fine when no space is added.
// Expected behavior
concurrently \"nginx\"
[0] nginx: [emerg] invalid number of arguments in "user" directive in /data/etc/nginx/nginx.conf:2
[0] nginx exited with code 1
Thanks for the report.
Yeah the quote stripping logic didn't handle impaired quotes -- I pushed a fix for it.
If you add a trailing space, my fix will not make your command line run though: concurrently will receive 2 commands, \"nginx and \". That's because you're wrapping the quotes when you don't need to.
Concurrently v4.1.1
I've noticed that adding whitespace removes the last character of the command inputed.
e.g.
Although it works perfectly fine when no space is added.
I've also noticed an issue similar to this here: https://github.com/kimmobrunfeldt/concurrently/issues/118
Just wanted to report this. Thanks
The text was updated successfully, but these errors were encountered: