From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Upas: Complete date library conversion.
Date: Sat, 19 Sep 2020 18:51:04 -0700 [thread overview]
Message-ID: <02FE2FEF065AEC3B39902C5D0AF46C73@eigenstate.org> (raw)
In-Reply-To: <20200920014650.GA15162@alice>
> ori@eigenstate.org once said:
>> When parsing, this makes the following argument match fuzzily.
>> +When formatting, this is ignored.
>> Fuzzy matching means that all formats are tried, from most to least specific.
>> For example,
>
> The word "fuzzily" is a bit silly and this rule is not like
> approximate string matching nor fuzzy logic.
>
> How about:
>
> When parsing, all formats of the following argument are tried
> from most to least specific. For example, ?M will match January,
> Jan, 01, and 1, in that order. When formatting, this is ignored.
>
> Cheers,
> Anthony
I like that much better, thanks!
If there are revisions to the diff, I'll roll them in, if not,
it'll be in the commit.
next prev parent reply other threads:[~2020-09-20 1:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 18:53 ori
2020-09-19 18:55 ` [9front] " ori
2020-09-20 0:38 ` ori
2020-09-20 1:46 ` Anthony Martin
2020-09-20 1:51 ` ori [this message]
2020-09-20 3:34 ` ori
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02FE2FEF065AEC3B39902C5D0AF46C73@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/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.
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 NNTP newsgroup(s).