Regexps suddenly case-sensitive?

2009-10-02 Thread Joost Kremers
Hi all,

I recently upgraded from Slackware 12.2 to Slackware 13.0. I installed mutt
1.5.20 from source both on the old and on the new system. I copied over my mutt
config files to the new system, so they are identical.

For some reason, since I did the OS upgrade, mutt's regular expressions are
case-sensitive. I noticed this with several hooks that use regexps and also with
the variable reply_regexp, which all of a sudden doesn't match capitalized
Re:  anymore, with the result that when I reply to a message, an additional
Re:  is added to the subject line, even if it begins with Re:  already. I
hadn't changed it from the default value, which always worked fine.

I changed reply_regexp to ^(Re([\\[0-9\\]+])*|Aw):[ \t]*, and then noticed
some more odd behaviour. If I'm in a remote IMAP mailbox, the regexp still
doesn't do its job. If I hit 'r' to reply to a message, an additional Re: 
gets appended to the subject. But if I copy the message to a local mail box (all
mbox in my case) and reply from it there, suddenly it works and no extra Re: 
is added.

Anyone have an idea what might be the cause of this? Like I said, I had no such
problem on slackware 12.2, it only started happening the past few days since the
upgrade, even though I'm running the same mutt version with the same config
files...

TIA

Joost


-- 
Joost Kremers
Life has its moments


Re: Regexps suddenly case-sensitive?

2009-10-02 Thread David Champion
* On 02 Oct 2009, Joost Kremers wrote:
 For some reason, since I did the OS upgrade, mutt's regular
 expressions are case-sensitive. I noticed this with several hooks
 that use regexps and also with the variable reply_regexp, which all
 of a sudden doesn't match capitalized Re:  anymore, with the result
 that when I reply to a message, an additional Re:  is added to the
 subject line, even if it begins with Re:  already. I hadn't changed
 it from the default value, which always worked fine.

A regex that is all lowercase matches insensitively.  A regex that
contains uppercase is case-sensitive.


 I changed reply_regexp to ^(Re([\\[0-9\\]+])*|Aw):[ \t]*, and then noticed

Use ^(re([\\[0-9\\]+])*|aw):[ \t]* and see whether the behavior
changes.

-- 
 -D.d...@uchicago.eduNSITUniversity of Chicago


Re: Regexps suddenly case-sensitive?

2009-10-02 Thread Omari Norman
On Fri, Oct 02, 2009 at 02:20:35PM +0200, Joost Kremers wrote:
 I recently upgraded from Slackware 12.2 to Slackware 13.0. I installed mutt
 1.5.20 from source both on the old and on the new system.
 For some reason, since I did the OS upgrade, mutt's regular expressions are
 case-sensitive.

I had a similar problem. How did you complile the newer Mutt--did you
modify the Slackbuild? See

http://dev.mutt.org/trac/ticket/3341

which may nor may not help you...


-- 
You can't lose what you never had.


Re: Regexps suddenly case-sensitive?

2009-10-02 Thread Joost Kremers
On Fri, Oct 02, 2009 at 10:26:28AM -0500, David Champion wrote:
  I changed reply_regexp to ^(Re([\\[0-9\\]+])*|Aw):[ \t]*, and then noticed
 
 Use ^(re([\\[0-9\\]+])*|aw):[ \t]* and see whether the behavior
 changes.

That's the default setting, which I had never changed, so it's the one that
causes the behaviour...


-- 
Joost Kremers
Life has its moments


Re: Regexps suddenly case-sensitive?

2009-10-02 Thread Joost Kremers
On Fri, Oct 02, 2009 at 11:37:34AM -0400, Omari Norman wrote:
 On Fri, Oct 02, 2009 at 02:20:35PM +0200, Joost Kremers wrote:
  I recently upgraded from Slackware 12.2 to Slackware 13.0. I installed mutt
  1.5.20 from source both on the old and on the new system.
  For some reason, since I did the OS upgrade, mutt's regular expressions are
  case-sensitive.
 
 I had a similar problem. How did you complile the newer Mutt--did you
 modify the Slackbuild?

I took the Slackbuild from the Slackware source tree for mutt 1.4.something. All
I changed was the version and build numbers in the Slackbuild, nothing else.

 See
 
 http://dev.mutt.org/trac/ticket/3341
 
 which may nor may not help you...

Thanks, it did. :-)

I first removed --enable-locales-fix and --without-wc-funcs, which solved the
problem for local mail boxes, but not for IMAP mail boxes. Then I removed
--enable-pop, and for some reason, now it works again in IMAP mail boxes as
well...

Why the POP3 code should have this effect is beyond me, but there it is...


-- 
Joost Kremers
Life has its moments