Re: imap/2182: segFault on imaps folder change with mailboxes=.
The following reply was made to PR imap/2182; it has been noted by GNATS.
From: Brendan Cully <brendan@xxxxxxxxxx>
To: Paul Walker <paul@xxxxxxxxxxxxxxxxxxxxx>
Cc: bug-any@xxxxxxxxxxxxx
Subject: Re: imap/2182: segFault on imaps folder change with mailboxes=.
Date: Mon, 3 Apr 2006 17:09:22 -0700
On Tuesday, 04 April 2006 at 01:03, Paul Walker wrote:
> On Tue, Apr 04, 2006 at 01:31:22AM +0200, Brendan Cully wrote:
>
> > Whoops, I think I may have just committed an equivalent patch to close
> > debian bug #351337 :) Can anyone confirm unpatched CVS fixes the bug?
>
> From looking at it, it won't crash any more. The other main difference I can
> see is that the one I submitted simply continues if a NULL mbox is given,
> while yours copies "INBOX" instead. I have two questions with that:
>
> a) is mutt smart enough to cache the results, or will it potentially ask the
> server twice for the same data?
yeah, from the other bug I think it'll cache the results. There might
be a mix-up if you have both imap://foo and imap://foo/INBOX in your
buffy-list - I haven't checked that. If the imap buffy parser calls
imap_fix_path everything should be fine.
> b) if people see INBOX showing up in their mailboxes list when they do
> "mailboxes = foo", there's a risk they're going to use "=" as an inbox
> shortcut elsewhere, and get confused when it doesn't work.
You won't see INBOX, you'll see $folder, which in the case of these
bugs was probably imap://server.
= and + always expand to $folder, so I don't think this is
inconsistent.