51–60 of 175 posts
Earlier quoted context omitted.
Yeah I'm more of a `--wet-run` `-w` fan myself. But it does depend on how serious/annoying the opposite is.
I've done that, but I hate the term "wet run." I use "live run" now, which I think gets the point across without being sort of uncomfortable.
I’m interested to know the etymology and history of the term. Somehow I imagine an inked printing press as the “wet run.”
I usually do the opposite and add a --really flag to my CLI utilities, so that they are read-only by default and extra effort is needed to screw things up.
I've committed "--i-meant-that" (for a destroy-the-remote-machine command that normally (without the arg) gives you a message and 10s to hit ^C if you're not sure, for some particularly impatient coworkers. Never ended up being used inappropriately, which is luck (but we never quantified how much luck :-)
I guess the goal for both is to give the user a chance to get out of autopilot, and avoid up-arrowing and re-executing.
Earlier quoted context omitted.
I've done that, but I hate the term "wet run." I use "live run" now, which I think gets the point across without being sort of uncomfortable.
--with-danger --make-it-so --do-the-thing --go-nuts --safety-off So many fun options.
What if the tool required an "un-safeword" to do destructive things? "Do you really want to 'rm -rf /'? Type 'fiberglass' to proceed."
Sort of a strange article. You don't see that many people _not_ praising --dry-run (speaking of which, the author should really learn to use long options with a double dash).
Quite handy.
I use --dry-run when I'm coding and I control the code. Otherwise it's not very wise to trust the application on what should be a deputy responsibility. Nowadays I'd probably use OverlayFS (or just Docker) to see what the changes would be, without ever risking the original FS.
Earlier quoted context omitted.
--with-danger --make-it-so --do-the-thing --go-nuts --safety-off So many fun options.
I've done a few --execute --i-know-what-im-doing for some more dangerous scripts