Year, formerly Y2K compliant, is no longer

[scruss]

Docs say:

y [YYYY]      Set the target Year to calculate for. 2000 to 2099.

However:

sunwait report 43.70011N 79.4163W d 21 m 1 y 2024
Error: "Year" must be between 0 and 99: 2024

As noted in many other issues, the date is off by one, always.

I still think your last version from ~2004 is far preferable to any later "improvements": https://web.archive.org/web/20130202223741/http://www.risacher.org/sunwait/

[treymd]

I have to rewrite my scripts that calculate dates and times to run my indoor garden due this change. Not sure why a 2 digit year was chosen but alas.... To the author: development whims have consequences.

[gsauthof]

What to you mean with 'As noted in many other issues, the date is off by one, always'?

When I run ./sunwait report 43.70011N 79.4163W d 21 m 1 y 24 I get:

                   Location:  43.700110N, 280.583700E
                       Date: 21-Jan-2024
                   Timezone: CET

What timezone do you have configured on your system?

[scruss]

What to you mean with 'As noted in many other issues, the date is off by one, always'?

Including, but not limited to:

• day off by one? · Issue #41 · risacher/sunwait
• Report printing wrong date. when reporting for a future date it incorrectly prints a date 1 day earlier. · Issue #17 · risacher/sunwait

I'm on EDT. I get:

                   Location:  43.700110N, 280.583700E
                       Date: 20-Jan-2024
                   Timezone: EST

280 degrees east? Aye, that'll be right ...