Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: amit.kucheria@gmail.com (Amit Kucheria)
Subject: [sup-talk] Dynamic list of maildir folders as sources
Date: Thu, 3 Sep 2009 17:26:40 +0300	[thread overview]
Message-ID: <20090903142640.GB4465@matterhorn.verdurent.com> (raw)

Hi,

I've been watching sup for a while and finally decided to take the plunge
today.  Apologies for the long-winded explanation before the real question,
but I guess if something in my workflow could be optimised, someone might be
able to point it out here.

I'll be running sup on a bunch of maildir folders downloaded via offlineimap.

All my mail comes as IMAP from 3 gmail accounts. When I subscribe to a new
mailing list, I simply create a new filter in gmail to add a new tag to email
from that list and skip the inbox. This shows up as a new maildir folder on my
local machine.

Mutt finds this new folder using the following folder-hook hack I have in my
.muttrc:

folder-hook +foo.* mailboxes `find ~/Mail/foo -type d
-name cur -type d -printf '%h\n' | sort | tr '\012' ' '`

, where foo is one of my mailboxes. So I have ~/Mail/bar and ~/Mail/foobar for
my other accounts. Each of these have several maildir folder in them.

I've run sup-config and it seems to expect that I list every maildir folder
I've got. Is there a way to generate this dynamically?

Regards,
Amit
p.s. sup-sync has been at it on my lkml folder with ~40K mail messages for
30mins now.
-- 
------------------------------------------------------------
Amit Kucheria
------------------------------------------------------------


             reply	other threads:[~2009-09-03 14:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03 14:26 Amit Kucheria [this message]
2009-09-03 15:37 ` William Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090903142640.GB4465@matterhorn.verdurent.com \
    --to=amit.kucheria@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox