Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: vasudeva@linkswarm.com (vasudeva)
Subject: [sup-talk] new user of sup
Date: Wed, 31 Oct 2007 14:05:10 -0400	[thread overview]
Message-ID: <20071031180510.GA7449@lenin.sovietwar.org> (raw)
In-Reply-To: <4728B67A.7020604@gslab.com>

* on 10-31-07, Manish Sapariya wrote:
>  - I configured two sources, however sup only keeps the last
> added source. I tried modifying sources.yaml, but it did not
> help. I have my TB configured with various rules to move all
> of my mails to different folders and I want to read all of
> these mboxes into sup. Is this a known bug? If yes, is there
> any workaround.

I had an issue like this, and found it to be related somehow to the
following lines being present in my ~/.sup/sources.yaml...

- !masanjin.net,2006-10-01/Redwood/SentLoader
  cur_offset: 29245
- !masanjin.net,2006-10-01/Redwood/DraftLoader
  cur_offset: 4

It seems if I snipped those out, then sup-add would actually add all
the sources I told it, not simply the final one. That is, if those
lines were present, sup-add seemed to overwrite any recently-added
source with the next source I'd add. (The two lines get generated
and replaced by sup at some point.)

Not sure if this is relevant to your issue, but the symptoms do
sound similar.



/></

--
linkswarm.com :: Collaborative Insolence
vasudeva.linkswarm.com/gallery :: For The Faint of Heart



  reply	other threads:[~2007-10-31 18:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 17:08 Manish Sapariya
2007-10-31 18:05 ` vasudeva [this message]
2007-11-02  4:02   ` William Morgan
2007-11-13  0:13   ` William Morgan
2007-11-13 18:41     ` vasudeva
2007-11-26 20: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=20071031180510.GA7449@lenin.sovietwar.org \
    --to=vasudeva@linkswarm.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