<story><title>Why does man print “gimme gimme gimme” at 00:30?</title><url>https://unix.stackexchange.com/questions/405783/why-does-man-print-gimme-gimme-gimme-at-0030</url></story><parent_chain></parent_chain><comment><author>craigc</author><text>I think people here need to lighten up. I know we are all programmers, and we are sometimes portrayed as snobby and entitled, but we don&amp;#x27;t have to live up to those stereotypes.&lt;p&gt;I understand it&amp;#x27;s frustrating when a tool you use is expected to work a certain way and it doesn&amp;#x27;t. I understand it&amp;#x27;s even more frustrating when the output could change depending on the time of day. That doesn&amp;#x27;t mean it is our place to gang up on an open source tool that is designed to make our lives easier.&lt;p&gt;I think we should be allowed to have some fun every once in a while, and this &amp;quot;gimme gimme gimme&amp;quot; easter egg  is awesome.&lt;p&gt;It seems the maintainers didn&amp;#x27;t realize that this easter egg was affecting a command that was designed to have a predictable output so that is the real issue here. Just a simple bug. If this was output on some help screen or something like that then no one would be complaining.</text></comment>
<story><title>Why does man print “gimme gimme gimme” at 00:30?</title><url>https://unix.stackexchange.com/questions/405783/why-does-man-print-gimme-gimme-gimme-at-0030</url></story><parent_chain></parent_chain><comment><author>Omnius</author><text>Year&amp;#x27;s ago i was coding a warehouse management system and in this edge case, that required a moon full and blood sacrifice to even have it occur i stuck some debug code&amp;#x2F;message that was only ever meant for me to try and figure out how it was happening.&lt;p&gt;5 years later i get a call. &amp;quot;We have a weird error message it says ... How did i even get here! This error is bad and you should feel bad.&amp;quot;</text></comment>