On Wed, Dec 21, 2022 at 11:07:26AM +0100, Tommy Pettersson
<[email protected]> wrote:
> I'm not subscribed to the list, sorry.
No problem :)
> I used rclock for reminders a long time ago, and recently
> tried it again, but could not get it to work. It is the
> parsing of year numbers that is not working when
> CENTURY=2000.
>
> Patch attached to make it work with any CENTURY.
I agree, this probably broke when I ported it from rxvt, and thus
the "TODO: verify" comment (the 2000 was suggested in the features
documentation, a pity that it doesn't work).
Seems you verified it, and it doesn't work (my rclock entries all use "*",
so I never noticed).
> I don't understand the logic of the old way, and it's clearly not working
> unless
> CENTURY == 1900.
I think for backwards compatibility (which kind of was the goal in
providing urclock in the first place), the better fix would be to restore
CENTURY to 1900, so as for it be compatible with existing rclock files.
This change will be in the next release.
I hope this resolves the problems this caused for you, and hopefully at some
time we can provide an optional better syntax.
Adding an extension to allow iso/international format (i.e. 4-digit year,
month, day in that order) is something I am contemplating for a while, but
of course it's not trivial to retro-fit this without breaking backwards
compatibility (and it took me a decade or so to provide urclock, so things
move quite slow :). This would also fix any year issues.
Greetings,
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/mailman/listinfo/rxvt-unicode
