News for hackers. Stuff that matters.

A comment on Command Line Interface Guidelines. Parent comment

Re:Command Line Interface Guidelines by kjs3 on Tuesday February 06, 2024 @11:44AM (#39276614)
If it operated differently based on what it was outputting to, that kinda defeats the point of 'dry run', which is to see exactly what's going to happen based on what's on the other side of the pipe when I run it for real. "Did this blow up because it's a bad command, or because there's a bug in the 'only kinda real dry run' code?".
[ Parent | on HN ]
Re:Command Line Interface Guidelines by samstave on Tuesday February 06, 2024 @04:10PM (#39280660)
+++

-

What if there wasa 'deep-pipe' '||' which would be based on a set env/docker/blah - which would launch an env and execute your '||'d code in it, and output some log/metrics/whatever?

[ Parent | on HN ]