From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: small patch for nnmail (lowercase expand option)
Date: Mon, 12 Jul 2004 15:33:41 +0900 [thread overview]
Message-ID: <b9yfz7xzqd6.fsf@jpl.org> (raw)
In-Reply-To: <b9yllhu54qh.fsf@jpl.org>
>>>>> In <b9yllhu54qh.fsf@jpl.org> Katsumi Yamaoka wrote:
>>>>>> In <87y8luhz6i.fsf@real.com>
>>>>>> dhedbor@real.com wrote:
>> +(defcustom nnmail-split-fancy-lowercase-expanded nil
> Is the option really needed? The value seems always one good at
> T because users cannot do case-sensitive splitting.
I've installed it with the default value T, considering no one
can decide whether to delete it. Since it affects not only the
fancy mail splitting but the standard one, I changed the variable
name into:
nnmail-split-lowercase-expanded
Regards,
next prev parent reply other threads:[~2004-07-12 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 23:06 dhedbor
2004-07-08 23:11 ` dhedbor
2004-07-09 1:49 ` Katsumi Yamaoka
2004-07-09 13:07 ` Marcelo Toledo
2004-07-09 15:49 ` Katsumi Yamaoka
2004-07-12 6:33 ` Katsumi Yamaoka [this message]
2004-07-12 17:08 ` dhedbor
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=b9yfz7xzqd6.fsf@jpl.org \
--to=yamaoka@jpl.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).