From: D. Goel <deego@glue.umd.edu>
Subject: Re: Keeping interesting messages
Date: 07 Jun 2002 15:35:22 -0400 [thread overview]
Message-ID: <ap33cvyopad.fsf@student1.physics.umd.edu> (raw)
In-Reply-To: <it4v8bw6.fsf@morpheus.demon.co.uk>
in addition to all the other replies,
somewhat related/unrelated---
i discovered the joys of caching recently..
viz. pressing * on an article does not let it go away when your
news-server wants to delete it after some time..
moreove, this article shows up with that "*" mark on it.. whether
read or unread.. , thus showing you that this is an article that
'interested' you and you cached...
(press * again to uncache..)
DG <http://www.glue.umd.edu/~deego/>
--
It is only the work of idealists that create surroundings in which
idealism is no longer necessary to let the good choices prevail.
-- David Kastrup on 'Free Software vs. Conveninent Software'
next prev parent reply other threads:[~2002-06-07 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 13:19 Paul Moore
2002-06-07 14:33 ` Frank Schmitt
2002-06-07 14:56 ` Josh Huber
2002-06-07 19:35 ` D. Goel [this message]
2002-06-07 20:43 ` Dheeraj Reddy
[not found] ` <vafvg8urjao.fsf@lucy.cs.uni-dortmund.de>
2002-06-07 20:52 ` Paul Moore
2002-06-08 11:32 ` Kai Großjohann
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=ap33cvyopad.fsf@student1.physics.umd.edu \
--to=deego@glue.umd.edu \
/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;
as well as URLs for NNTP newsgroup(s).