user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: [RFC 0/2] watch behavior changes aNd ProPoSaL
Date: Thu, 23 Apr 2020 08:34:17 +0000	[thread overview]
Message-ID: <20200423083419.835-1-e@yhbt.net> (raw)

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.

But, mutt allows POSIX regexps...  I'm not sure if regexps are
necessary for this, and I also don't want this to be tied to
Perl/PCRE in case we or someone else wants to use another
language/runtime.  We can't use POSIX regexps from Perl w/o
XS from CPAN or Inline::C, so more crap to force on the user.

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

Or, add a new option:

	watchHeaderInsensitively = To:John Smith

Ugh...

Eric Wong (2):
  watchmaildir: scan all matching headers
  watchmaildir: match List-ID case-insensitively

 lib/PublicInbox/WatchMaildir.pm | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

             reply	other threads:[~2020-04-23  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23  8:34 Eric Wong [this message]
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 ` [RFC 0/2] watch behavior changes aNd ProPoSaL Kyle Meyer

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=20200423083419.835-1-e@yhbt.net \
    --to=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).