Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Dynamic list of maildir folders as sources
Date: Thu, 03 Sep 2009 08:37:50 -0700	[thread overview]
Message-ID: <1251991617-sup-9735@masanjin.net> (raw)
In-Reply-To: <20090903142640.GB4465@matterhorn.verdurent.com>

Reformatted excerpts from Amit Kucheria's message of 2009-09-03:
> I've been watching sup for a while and finally decided to take the
> plunge today.

Welcome!

> 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?

If you can generate the list (e.g. with the find command you cited), you
can add maildir sources with sup-add directly, instead of having to go
through sup-config.

If you want to automatically detect and add new folders, we could d
something similar in the startup hook. Something like (completely
untested):

  dirs = `find ~/Mail/whatever...`
  dirs.each do |d|
    uri = "maildir:#{d}"
    log "trying #{uri}..."
    unless SourceManager.source_for uri
      source = Maildir.new uri
      SourceManager.add_source source
      log "Added #{uri}"
    end
  end

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

Yep, indexing stuff is slow. FWIW, you only have to do it once, and
there are new index backends that are significantly faster. (But still
far from instantaneous.)
-- 
William <wmorgan-sup at masanjin.net>


      reply	other threads:[~2009-09-03 15:37 UTC|newest]

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

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=1251991617-sup-9735@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    /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