From: Devon Gleeson <dgleeson@tripwire.com>
To: Alexander Klink <alexander@klink.name>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Programmatically removing tags (:inbox)
Date: Thu, 24 Apr 2014 18:00:16 +0000 [thread overview]
Message-ID: <1398362146-sup-1442@dgleesonlnx> (raw)
In-Reply-To: <1398267413-sup-3348@zoe>
I had this problem too when I first started using Sup. I think what I
ended up having to do was force sup to load all messages into memory
with !!, then tag all with T, then removed inbox. I took a long time for
sup to churn through all of that, but it did work eventually.
IDK, this does seem like a barrier to entry for new folks trying to
adopt sup.
--
Devon Gleeson
Software Engineer
TRIPWIRE | CONFIDENCE:SECURED
www.tripwire.com
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2014-04-24 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 15:42 Alexander Klink
2014-04-23 16:24 ` MaDhAt2r
2014-04-24 8:55 ` Alexander Klink
2014-04-23 18:11 ` Matthieu Rakotojaona
2014-04-24 13:17 ` Alexander Klink
2014-04-25 10:53 ` Gaute Hope
2014-05-02 9:08 ` Gaute Hope
2014-04-24 18:00 ` Devon Gleeson [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=1398362146-sup-1442@dgleesonlnx \
--to=dgleeson@tripwire.com \
--cc=alexander@klink.name \
--cc=sup-talk@rubyforge.org \
/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