From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] an error occurred in Sup
Date: Fri, 28 Aug 2009 13:38:59 -0700 [thread overview]
Message-ID: <1251491856-sup-4902@masanjin.net> (raw)
In-Reply-To: <1251316321-sup-8091@clover.schedar.com>
Reformatted excerpts from Stan Heckman's message of 2009-08-26:
> I had told sup-config about my existing maildirs. This produced a
> large inbox. I attempted to archive all but 15 recent messages from
> this inbox by loading all messages with "!!" and archiving them all by
> holding down the "a" key for several seconds.
Definitely the slow an painful way to do this, and also the way to
trigger one of the display threading heisenbugs.
I recommend instead using sup-tweak-labels, or starting over and using
--archive when you sup-add the source (and then just adding the inbox
label back to the first 15).
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-08-28 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 19:59 Stan Heckman
2009-08-28 20:38 ` 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=1251491856-sup-4902@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