Re: Non-recurring Events in calendar(1)

On Thu, May 29, 2025 at 02:40:38PM -0000, Stuart Henderson wrote:
> On 2025-05-29, Jason McIntyre <jmc@kerhand.co.uk> wrote:
> > On Wed, May 28, 2025 at 07:29:57AM +0200, Carsten Reith wrote:
> >> On Tue, May 27, 2025 at 03:22:56PM -0400, Allan Streib wrote:
> >> > On Tue, May 27, 2025, at 15:20, Allan Streib wrote:
> >> > > The man page for calendar says:
> >> > >
> >> > > Other lines should begin with a month and day.
> >> >
> >> > Sorry, fat fingered and sent before completing my thought.
> >> >
> >> > This implies that year is ignored. Looking at files in /usr/share/calendar
> >> > also supports this.
> >> >
> >> > Allan
> >> >
> >>
> >> As Richard, I missed the implication, especially as the description of the '-t'
> >> option discusses the year format.
> >>
> >> Maybe an additional sentence in the man page won't do no harm ?
> >>
> >>
> >> Index: calendar.1
> >> ===================================================================
> >> RCS file: /cvs/src/usr.bin/calendar/calendar.1,v
> >> diff -u -p -u -p -r1.45 calendar.1
> >> --- calendar.1 21 Feb 2025 19:04:34 -0000 1.45
> >> +++ calendar.1 28 May 2025 05:17:54 -0000
> >> @@ -130,7 +130,8 @@ A day without a month matches that day o
> >> A month without a day matches the first of that month.
> >> Two numbers default to the month followed by the day.
> >> Lines with leading tabs default to the last entered date, allowing
> >> -multiple line specifications for a single date.
> >> +multiple line specifications for a single date. A year can be specified, but
> >> +it will be ignored in the output.
> >> .Dq Easter
> >> (may be followed by a positive or negative integer) is Easter for this year.
> >> .Dq Paskha
> >>
> >
> > hi.
> >
> > i don;t understand the diff:
> >
> > $ cat calendar
> > May 30 2025 It's the 30th
> > $ calendar
> > It's the 30th
> > $ calendar -t 20260530
> > It's the 30th
> >
> > have i misunderstood the intent?
> >
> > jmc
> >
> >
>
> "it will be ignored _in the output_" doesn't make sense, it does
> does matter for the output:
>
> $ printf 'Easter-2\tGood Friday\n' > calendar
> $ $ calendar -t 20240329
> Mar 29* Good Friday
> $ calendar -t 20250329
> $ calendar -t 20250418
> Apr 18* Good Friday
>
> it's just that a year, if present, is simply not parsed at all when
> reading the input calendar file.
>
> --
> Please keep replies on the mailing list.
>

thanks stuart.

so essentially the diff doesn;t make sense, right? so i can drop it...
jmc