My findings so far:
(Never mind RFC errors I mentioned. That was an unrelated side effect of
me trying to mail error output with mail -s with newlines in the subject.)
calendar -f /dev/stdin
or calendar -f <(...)
will not work for anybody without any calendar files on their account,
including root.
To be safe one needs to only use real files with -f, otherwise the -f /dev/stdin
might get ignored, and instead just spew out plain `calendar` output!
You might want to document or fix this bug of -f, lest one move ones
scripts to an account with no other calendar files, and have them blow up.
CALENDAR_DIR= calendar ...
won't help and disables any action.
P.S., You might want to cut down on these repeated calls if possible:
# strace calendar 2>&1|sort|uniq -c|sort -nr|head
292 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=724, ...}) = 0
3 close(5) = 0
3 Sep 05...
You might want to implement --help,
# calendar --help
calendar: invalid option -- 'h'
usage: calendar [-ab] [-A num] [-B num] [-l num] [-w num][-f calendarfile] [-t
[[[cc]yy][mm]]dd]
And put a space .........................................^ here
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
