From: Anthony Martinez <pi+sup@pihost.us>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] listing archived threads
Date: Tue, 01 Jun 2010 16:59:25 -0700 [thread overview]
Message-ID: <1275436473-sup-2083@home.mrtheplague.net> (raw)
In-Reply-To: <1275433722-sup-8872@terrapin.truxton.com>
Excerpts from Truxton Fulton's message of Tue Jun 01 16:16:46 -0700 2010:
> 'sup sup users!
> I'm new to sup.
> Can anyone tell me how to list archived threads?
An archived thread is just one that isn't marked with an `inbox' label.
> deleted threads get a "deleted" label by which they may be listed
> (with the L command)
> But there is no "archived" label...
Do a search for "!inbox" or "before:tomorrow" or the like.
> Thanks,
>
> -Truxton
No problem,
Pi
--
Several recent languages have adopted an Intercal-like, asynchronous, computed
COME-FROM concept. Only they refer to it with funny terms like "exception
handling". -- Hans Mulder
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-06-02 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 23:16 Truxton Fulton
2010-06-01 23:59 ` Anthony Martinez [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=1275436473-sup-2083@home.mrtheplague.net \
--to=pi+sup@pihost.us \
--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