Adam Porter

Thanks for the kind words. I'm glad it's useful to you. Finding a co-maintainer is usually tricky. Users don't generally look at the repository unless they need to report a...

Thanks, that's cool. If I were to enable the wiki for this repo, would you contribute it there?

Please see `ts-internal`. > Some more readers would also be helpful, for plugging into interactive forms to avoid using the various string conversions in `diary-lib` etc. I can maybe upstream...

`seconds-to-time` is not documented in the Elisp manual for some reason, so it might be better to avoid using it. AFAICT `time-convert` is the newly designated function for this purpose,...

Forgive my pedantry, but there is so much jargon in this context, that it's helpful to me if we use only the official, "blessed" Emacs terms for these things, so...

> Unless I missed something `decode-time` always loses precision. Even if every slot is populated, they could destroy precision when used to update the unix and or internal time. Ok,...

Various benchmarks from earlier in `ts`'s development may be seen in the notes file: https://github.com/alphapapa/ts.el/blob/master/notes.org

Note, of course, that `decoded-time-` accessors did not exist in Emacs prior to `ts`. Those were added after `ts` had been released and used in the wild for some time....

> I do not see how unified API would justify ts struct (there are already too many time representations in Emacs; adding yet another one will be questioned). It may...

Here's a very simple initial example of how the `ts` API is easier to use to manipulate a timestamp than the current Emacs native ones: ```el (let ((decoded (decode-time argh-time)))...