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'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.
The text was updated successfully, but these errors were encountered:
@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.
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.
The text was updated successfully, but these errors were encountered: