First let me apologize for the bad diff. I pledge, I'll never write emails before having had the first coffee ...
On Fri, May 30, 2025 at 12:14:13AM +0100, Stuart Henderson wrote: > On 2025-05-29, Jason McIntyre <j...@kerhand.co.uk> wrote: > > so essentially the diff doesn;t make sense, right? so i can drop it... > > I think so. > > Basically it's "the parser is sloppy and doesn't error out on unexpected > input". > > The current manual describes what it does do (month and a day in various > formats, easter/paskha, the former with some +/- and some other variants, > or an empty column to repeat the previous parsed date, followed by a tab > and then description) but, in the usual tradition of most manuals, > doesn't describe what it doesn't do (e.g. years). > Let me try to explain my problem more clearly. Condider the following calendar file: hamlet$ cat testcal 06/06/2024 Project A - milestone1 05/30/2025 Project B - milestone1 06/15/2025 Project B - milestone2 Now the man page says for the -A option: " -A num Print lines from today and next num days (forward, future)." Now consider the following: hamlet$ date Fri May 30 08:54:52 CEST 2025 hamlet$ calendar -f testcal -A 20 May 30 Project B - milestone1 Jun 06 Project A - milestone1 Jun 15 Project B - milestone2 Now the entry "Jun 06 Project A - milestone1" lies in the past, not within "next num days (forward, future)". hamlet$ calendar -f testcal -t 2025/06/06 Jun 06 Project A - milestone1 hamlet$ calendar -f testcal -t 2024/06/06 Jun 06 Project A - milestone1 The -t option says: "-t [[[cc]yy]mm]dd [..] If yy is specified, but cc is not, a value for yy between 69 and 99 results in a cc value of 19". As far as I can see, the year is ignored completely. That's fine. But then the description for -t is at least misleading. Why should I want to specify a year if it is ignored anyway ?
