Daniel Kahn Gillmor writes:
> (sorry for the late reply to this thread)
>
> On Thu 2019-02-21 15:11:48 -0400, David Bremner wrote:
>> to be unique case-insensitively, so I decided to convert them to lower
>> case on input. This turns out to be "fun", if we try to handle things
>> other than
is happening, and prefer the
locale stored in the db.
I don't have the capacity to work on this kind of safeguard right now,
but someone who wants to learn more about locales and notmuch could try
to implement it and we could see what happens. Being explicit about the
concern like this might hel
David Bremner writes:
> Otherwise we could insist they are UTF-8, ignoring the locale. The
> fullest generality (I think) is to first convert from the users locale
> to utf8, as in the attached sample program. The gotcha is that the call
> to setlocale is necessary, and can't really be local to
So I've been revisiting the "user defined headers" [1] patches. I need
the in
$ notmuch config set index.header. "blah"
to be unique case-insensitively, so I decided to convert them to lower
case on input. This turns out to be "fun", if we try to handle things
other than ASCII. So one
