On 2025-05-30, Carsten Reith <carsten.re...@t-online.de> wrote: > 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
You are assuming that calendar(1) supports years in this field, but it does not, it only handles annually repeating events. The manual is already clear about what's supported here. > 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)". But Jun 06 *is* in the future, calendar(1) is just ignoring the invalid part of input when parsing the calendar file. > 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". a future Y2K69 problem lies in store :-) > 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 ? It's not ignored, it's used for Easter-based dates. -- Please keep replies on the mailing list.
