From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@yhbt.net>
Cc: meta@public-inbox.org
Subject: Re: [RFC 0/2] watch behavior changes aNd ProPoSaL
Date: Fri, 24 Apr 2020 03:12:36 +0000 [thread overview]
Message-ID: <87r1wdshjv.fsf@kyleam.com> (raw)
In-Reply-To: <20200423083419.835-1-e@yhbt.net>
Eric Wong <e@yhbt.net> writes:
> Now, I don't think the following two patches will cause any
> problems for existing users...
>
> Down the line, for matching non-List-ID headers insensitively,
> I'm thinking "mutt style" case-sensitivity is probably a good
> default. That is:
>
> Match case-sensitively iff capital letters exist in
> the substring. Otherwise, match case-insensitively.
Yeah, I find this behavior to be pretty intuitive/nice, though I guess
the only context where I've (knowingly) used it is Emacs search, so that
might discount my 2 cents :)
However, if it's either this or an option like...
> Otherwise, I'm not sure how a user should (or would care to)
> specify case-insensitivity vs case-sensitivity...
>
> Valid email headers names won't have spaces (or many other
> chars), so we can do somthing like attempt to parse out " -i"
> (like "grep -i"):
>
> watchheader = To -i:John Smith
... this, I guess this one has the advantage of being able to
case-sensitively match all lowercase? I'm not sure how much practical
value there is to that, though.
I think the -i proposal above is nicer than this next one, but I suppose
it'd have the same advantage.
> Or, add a new option:
>
> watchHeaderInsensitively = To:John Smith
>
> Ugh...
prev parent reply other threads:[~2020-04-24 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 8:34 [RFC 0/2] watch behavior changes aNd ProPoSaL Eric Wong
2020-04-23 8:34 ` [PATCH 1/2] watchmaildir: scan all matching headers Eric Wong
2020-04-23 8:34 ` [PATCH 2/2] watchmaildir: match List-ID case-insensitively Eric Wong
2020-04-24 3:12 ` Kyle Meyer [this message]
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: http://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=87r1wdshjv.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=e@yhbt.net \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.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).