From: Eric Wong <e@80x24.org>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 3/3] search: rectify comment (rt: documented since 738c4a65719e)
Date: Mon, 16 Oct 2023 21:39:46 +0000 [thread overview]
Message-ID: <20231016213946.M370695@dcvr> (raw)
In-Reply-To: <20231016113304.2788497-3-stepnem@smrk.net>
Štěpán Němec <stepnem@smrk.net> wrote:
> Fixes: 738c4a65719e ("www: various help text updates")
> ---
> On a related note, there's this comment in LeiXSearch.pm:312:
>
> # this should really be rt: (received-time), but no stable
> # public-inbox releases support it, yet.
> my $dt = 'dt:'.strftime('%Y%m%d%H%M%S', gmtime($lr)).'..';
>
> So I went all "hey, it's been 3 releases with rt:, let's do this",
> and suddenly, `lei up` stopped getting any updates :-]
> The problem is that the date syntax handling for d:, dt: and rt: is not
> the same (date_parse_prepare in Search.pm), which doesn't seem ideal to
> me, either, but maybe that's intentional/necessary?
Yeah, probably: "rt:$lr.."; is correct.
It's historical baggage since rt: wasn't really used until we
got IMAP (2020); and we didn't have user-friendly approxidate
parsing until 2021.
d: and dt: had to be at least usable before 2021, so it's more
usable in "raw" form.
It's expensive to reindex so it's not something I'm inclined to
force users into doing, either...
d: was a short-sighted mistake and redundant. I suppose we
could stop indexing d: at some point (like we do with --skip-docdata)
and translate all (not just most) d: into dt: in the parser.
> On a totally unrelated note, this patch is a nice example of how
> --diff-algorithm=histogram (which I use by default) sometimes produces
> diffs that are both longer and more confusing than with any other
> (git-provided) algorithm:
Heh, I've never touched --diff-algorithm. But I sometimes pipe
messages to `lei rediff -W' or `lei rediff -U100' to get more
context.
I hope to add support for rediff to the WWW UI once coderepo
integration is improved.
next prev parent reply other threads:[~2023-10-16 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 11:33 [PATCH 1/3] doc: fix some typos and grammar Štěpán Němec
2023-10-16 11:33 ` [PATCH 2/3] doc: lei-q: drop stale TODO comment (fixed in 1f1b1f0e22f7) Štěpán Němec
2023-10-16 21:17 ` Eric Wong
2023-10-16 11:33 ` [PATCH 3/3] search: rectify comment (rt: documented since 738c4a65719e) Štěpán Němec
2023-10-16 21:39 ` Eric Wong [this message]
2023-10-16 21:13 ` [PATCH 1/3] doc: fix some typos and grammar Eric Wong
2023-10-16 22:16 ` Štěpán Němec
2023-10-17 6:43 ` [PATCH 4/3] install/README: improve wording Eric Wong
2023-10-17 7:19 ` Štěpán Němec
2023-10-17 7:54 ` Eric Wong
2023-10-17 8:07 ` Štěpán Němec
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231016213946.M370695@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=stepnem@smrk.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.
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).