Skip to content
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

Syntax for benchmarking multiple commands #36

Open
hashimaziz1 opened this issue Oct 4, 2018 · 1 comment
Open

Syntax for benchmarking multiple commands #36

hashimaziz1 opened this issue Oct 4, 2018 · 1 comment

Comments

@hashimaziz1
Copy link

hashimaziz1 commented Oct 4, 2018

Hey there. Firstly, thanks for the great utility.

I'm confused by the syntax for benchmarking multiple commands, or rather the logic behind it, and the documentation is minimal doesn't explain any further. As far as I can tell, when benchmarking several commands, exactly one of the commands must be enclosed in quotes, and the others cannot be. This can be a little confusing logically, so I was wondering what the reason is for why it's done this way, and whether there's any difference in how benchmarking is done on the command in quotes compared to the other commands? Are there particular commands that should or should not be in quotes?

Thanks in advance, I'd really appreciate it.

@Gabriella439
Copy link
Owner

@Kaos-Industries: My understanding is that the number of commands does not affect whether or not they need quotes. Rather, they require quotes if the command contains more than one token. However, a good rule of thumb is to just quote all commands and not rely on the Bash shell's automatic quoting mechanism.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants