On Thu, Aug 29, 2002 at 02:00:30PM -0400, krjw wrote: > +-- On 29082002 12:16:11 +0000, darren chamberlain uttered: > | * krjw <[EMAIL PROTECTED]> [2002-08-29 11:57]: > | > | > 1) Firstly, does mutt support or will mutt ever support extended > | > maildirs? I've never seen extended maildirs 'till I started using > | > maildrop, but they're kinky. They allow for folders-within-folders > | > which is very handy.
this works. as a matter of fact i use it. i think iirc it works as far back as version 1.3. i use 1.5 now. what do you have setup for your spoolfile, mbox, mbox_type, folder? do you have bar and bar.blah set up as mailboxes? > FOO > FOO/tmp > FOO/new > FOO/cur > FOO/.bar > FOO/.bar/tmp > FOO/.bar/new > FOO/.bar/cur > FOO/.bar/maildirfolder > FOO/.bar.blah > FOO/.bar.blah/tmp > FOO/.bar.blah/new > FOO/.bar.blah/cur > FOO/.bar.blah/maildirfolder what happens if you use c and then type an absolute path to .bar or .bar.blah? a la /path/to/FOO/.bar > (maildirfolder is a regular file.) perhaps the existance of this file is what is throwing mutt off. have you tried removing it? what is it there for? > mutt sees FOO but has zero knowledge of bar or blah AFAICT. what do you mean, exactly? you can tell mutt that these are mailboxes by using the mailboxes command in your muttrc. a la mailboxes = /path/to/FOO mailboxes = /path/to/FOO/.bar mailboxes = /path/to/FOO/.bar.blah if you do this, you can use c and if there is new email in any of them mutt will automagically give it as the next choice. hth -- Peter Abplanalp Email: [EMAIL PROTECTED] PGP: pgp.mit.edu
msg30519/pgp00000.pgp
Description: PGP signature
