From: Eric Wong <e@yhbt.net>
To: Josh Natanson <josh@natanson.net>
Cc: clogger-public@yhbt.net
Subject: Re: Clogger request_time formatting
Date: Thu, 9 Jul 2020 22:57:46 +0000 [thread overview]
Message-ID: <20200709225746.GB23508@dcvr> (raw)
In-Reply-To: <CAPdx2syEU5WLBx9PezfQ6nFdpnouscXwnm-bg0+t5ERi7EPnJg@mail.gmail.com>
Josh Natanson <josh@natanson.net> wrote:
> > Or is the "." component not desirable?
>
> Exactly, my requirements require actual microseconds, not just that precision.
OK.
Btw, please keep clogger-public@yhbt.net Cc-ed for public
archival purposes. Most people reading these emails are not
subscribed via SMTP, but rather via NNTP/Atom/HTML/IMAP/git;
so we have no idea how many people read this inbox.
> > I suppose something like $request_time{6,0} could be added
> > (Multiply by 10**6, PRECISION=0)
>
> I think that would do the trick, but probably wouldn't be backwards
> compatible with people already using $request_time{6,0}? Maybe a
> second optional {}, like $request_time{0}{6}? Or a separate token
> altogether, $request_time_micro, but that could be less flexible.
There shouldn't be any incompatibility, since it currently
accepts only matching /\A\$request_time\{(\d+)\}\z/. Thus "{6,0}"
is rejected by current versions.
next prev parent reply other threads:[~2020-07-09 22:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 16:30 Clogger request_time formatting Josh Natanson
2020-07-09 20:28 ` Eric Wong
[not found] ` <CAPdx2syEU5WLBx9PezfQ6nFdpnouscXwnm-bg0+t5ERi7EPnJg@mail.gmail.com>
2020-07-09 22:57 ` Eric Wong [this message]
2020-07-26 4:46 ` Eric Wong
2020-07-27 15:15 ` Josh Natanson
2020-07-27 18:38 ` Eric Wong
2020-07-28 13:50 ` Josh Natanson
2020-07-29 9:20 ` Eric Wong
2020-07-29 19:50 ` Josh Natanson
2020-07-30 3:54 ` Eric Wong
2020-07-31 14:08 ` Josh Natanson
2020-07-31 14:09 ` Josh Natanson
2020-07-31 19:44 ` Eric Wong
2020-08-02 13:47 ` Josh Natanson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/clogger/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200709225746.GB23508@dcvr \
--to=e@yhbt.net \
--cc=clogger-public@yhbt.net \
--cc=josh@natanson.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/clogger.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).