Re: small patch for nnmail (lowercase expand option)

[dhedbor@real.com]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>>>>>> 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,
Katsumi Yamaoka <yamaoka@jpl.org> writes:

>>>>>> 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.

(seems like I missed a few mails here for some reason)

Perhaps the option isn't needed just because splitting is case
insensitive as you say. However I didn't want to supply a patch that
unconditionally changed the old behavior.

> 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

This is true, I didn't think about that since I never used this kind
of splitting before (pattern with replace) prior to using fancy
splitting.


-- 
David Hedbor, Software Development Engineer - Real Networks
Helix Community: http://helixcommunity.org