4 ms·
These are cool, and I use chronic all the time. But is there any more documentation beyond this page? I can't find any, and I'd love to read more about pee and
by pjungwir 12y ago
These are cool, and I use chronic all the time. But is there any more documentation beyond this page? I can't find any, and I'd love to read more about pee and see some examples. It seems there is more documentation for the rejected utilities than the accepted ones!
- avar 12y agoWhen you clone the Git repository and build the package all the utilities come with manual pages built from DocBook, e.g. for chronic: $ man ./chronic.1 | col -b | grep -v ^$ | head -n 12 CHRONIC(1) CHRONIC(1) NAME chronic - runs a command quietly unless it fails SYNOPSIS chronic COMMAND... DESCRIPTION chronic runs a command, and arranges for its standard out and standard error to only be displayed if the command fails (exits nonzero or crashes). If the command succeeds, any extraneous output will be hidden. A common use for chronic is for running a cron job. Rather than trying to keep the command quiet, and having to deal with mails containing accidental output when it succeeds, and not verbose enough output when it fails, you can just run it verbosely always, and use chronic to hide the successful output. 0 1 * * * chronic backup # instead of backup >/dev/null 2>&1
- pjungwir 12y agoAh, thanks! More people might use this if the author put those docs online and linked to them from the main page. I don't know docbook but it looks like styling it as HTML should be easy. Now I understand pee. I wrote something less generalized here: https://github.com/pjungwir/stutter https://github.com/pjungwir/stutter I guess `stutter foo` is equivalent to `pee cat foo`.