On Wed, Jan 26, 2000 at 02:13:23PM -0600, David DeSimone wrote:
> By the way, something to watch out for in .mutrrc's:
>
> set reply_regexp = "^(re|aw):[ \t]*"
>
> This doesn't do what you think it does; Mutt sees the "\t" as simply
> "t", because backslashes are parsed within double-quotes. So the regexp
> comes out as "^(re|aw):[ t]*", and so a subject like "Re: Tuesday" comes
> out with a real subject of "uesday". :)
I always wondered, how many backslashes I need in such places ;).
However my ~/.muttrc contains this:
set reply_regexp="^(re|aw)(\\[[0-9]+\\])?:[ \t]*" # TheBat! uses Re[%d]:
and when I query Mutt (:set ?reply_regexp), I see
reply_regexp="^(re|aw)(\[[0-9]+\])?:[ .]*"
I suppose that `.' in brackets is the actual tab character, so your warning
is not necessary in this case.
OTOH things like
send-hook '~C "\\<foo[^ ]*@"' ...
or
color index red default '~h "X-Note: Message-ID seen before recently\."'
are a different issue. I'm not quite sure how many `\'s should there
be before that `.' and I'm a little too lazy to experiment to find it
out. :-) (I'm sure a single \ there is not enough, but even an unescaped
dot would work for me there, and I don't expect many false matches.)
Marius Gedminas
--
F U cn rd dis U mst uz Unix.
