-
-
Notifications
You must be signed in to change notification settings - Fork 381
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
Add ability to avoid shell processing #428
Comments
Please see #336
It would be a possibility, but how would you do a multi-command benchmark? we would need some sort of separator argument:
which - to me - is even worse. Once we implement #336, we will only do simple string splitting for the arguments. So if you run |
The only place I'd want the above approach is when you don't use shell processing, as you could otherwise just pass the The linked #336 issue would honestly solve all of my needs though. I would just need things like |
Not sure if I explained it well. What I meant was: I want to compare the runtime of command1 with the runtime of command2. Right now, I can do it like this: hyperfine --show-output 'command1 --with --some --options' 'command2 --with --other --options' |
Yes. We would probably use https://crates.io/crates/shell-words to do proper splitting of arguments. |
I just got hyperfine installed on my system (sorry if I'm overlooking something obvious), but there doesn't seem to be any native way to avoid shell processing.
For example, I'd expect this to just print
${PWD}
, but alas it prints the currently directory of my terminal:hyperfine 'echo ${PWD}' --show-output
This also leads to another gripe with hyperfine I'm having: I'm not wanting to put the entire command I'm wanting to use inside of quotes. I'd much prefer to do something like this, and have the arguments get passed to the command in question without processing by a shell:
The text was updated successfully, but these errors were encountered: