Date: Tue, 11 May 2010 14:16:27 +1000 From: andrew clarke <mail@ozzmosis.com> To: David Allen <the.real.david.allen@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: md5(1) and cal(1) Message-ID: <20100511041627.GA87743@ozzmosis.com> In-Reply-To: <AANLkTil779I9T4JhvaHgCCYkbSTz4xoqzjGv6wYVpYaR@mail.gmail.com> References: <AANLkTil779I9T4JhvaHgCCYkbSTz4xoqzjGv6wYVpYaR@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon 2010-05-10 17:35:45 UTC-0800, David Allen (the.real.david.allen@gmail.com) wrote: > 1. Why doesn't cal(1) hilight the current day? Hell, some days I'm > not even sure what day or week it is, so after typing 'cal', I have to > type in 'date', and then sit there for a few seconds to interpret what > I'm looking at. Of course, that isn't always successful, so I > typically end up reaching for my mouse and hilight the date manually. > But after doing that I'm just as annoyed by not knowing the date as > I'm annoyed by the behavior of the cal utility and the extra work I'm > forced to do. cal(1) is pretty old. I suspect it was written partly so the output could be printed out on paper. /usr/ports/deskutils/cal might be more your taste. > 2. Why doesn't md5(1) have a "check" option? Seems to me requiring a > manual inspection is error-prone at best, and makes scripting unecessarily > complicated. If you're comparing two files, cmp(1) might be more suitable.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100511041627.GA87743>