4 ms·
I would have added this "feature" with a mechanism to detect if it's running inside a TTY. That way, automated tests, pipes or scripts that parse the output wou
by fermuch 9y ago
I would have added this "feature" with a mechanism to detect if it's running inside a TTY. That way, automated tests, pipes or scripts that parse the output wouldn't have this problem.
But seriously, who uses a documentation tool for automated tests every minute? That use case is just insane and out of the scope of man IMHO.
- k__ 9y agoThey also used it without specifying a page.
- Thagor 9y agoThere was still a true bug because "gimme gimme gimme" appeared when calling "man -w", and that's the command they were using. But I still don't understand how a test could break because of this.
- _jal 9y ago> But seriously, who uses a documentation tool for automated tests every minute? As someone with a long history of abusing tools and side-effects, I'll defend that. The whole point of the Unix philosophy is small, useful tools that can be composited in ways the creator never anticipated. If it works for them, great. (At least until it isn't.) But then I also pry with my pocketknife, and you probably don't want to know how about using a mill engine as a come-along...
- JadeNB 9y ago> But seriously, who uses a documentation tool for automated tests every minute? That use case is just insane and out of the scope of man IMHO. It seems that it's not being triggered every minute: https://unix.stackexchange.com/questions/405783/why-does-man-print-gimme-gimme-gimme-at-0030#comment726350_405783 https://unix.stackexchange.com/questions/405783/why-does-man... . (In fact, I can't find, even in the pre-editing version of the post, any reference to it happening every minute; but probably I'm just missing it.)