From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: Keeping interesting messages
Date: Fri, 07 Jun 2002 10:56:31 -0400 [thread overview]
Message-ID: <87d6v3b0io.fsf@alum.wpi.edu> (raw)
In-Reply-To: <it4v8bw6.fsf@morpheus.demon.co.uk>
Paul Moore <gustav@morpheus.demon.co.uk> writes:
> One thing I'm still not sure of the best way to handle, though. I'd
> like to be able to "keep" messages and news articles that interest me
> - possibly for a long time, possibly just for a few days (until I get
> a chance to deal with it). I don't want to leave the messages
> unread, as that interferes with my normal scan-read-catchup approach
> to reading groups. I'd rather keep the messages either in their
> original groups, or in some sort of "parallel" arrangement, so I
> don't lose track of where they came from.
This is what I do:
a) for messages I'm going to reply to, I immediately hit R C-c C-d if
I don't have time to reply right away. (which is almost always)
Then, the message is sitting in my drafts folder.
b) for saving interesting messages, I use a little function I wrote:
;; bind a key that copies an article to the group
;; archive.<groupname>
(defun jmh:save-archive ()
(interactive)
(let ((group-name (if (string-match ":" gnus-newsgroup-name)
(substring gnus-newsgroup-name (match-end 0))
gnus-newsgroup-name)))
(gnus-summary-copy-article 1 (concat "archive." group-name))))
(add-hook 'gnus-summary-mode-hook
'(lambda ()
(local-set-key (kbd "C-c s") 'jmh:save-archive)
(local-set-key (kbd "C-c p") 'jmh:forward-to-spamcop)))
This way, if I want to save a message for longer-term, I just hit C-c
s.
Also, be sure to add whatever your archive groups are called to the
gnus-auto-subscribed-groups regexp.
ttyl,
--
Josh Huber
next prev parent reply other threads:[~2002-06-07 14:56 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 [this message]
2002-06-07 19:35 ` D. Goel
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=87d6v3b0io.fsf@alum.wpi.edu \
--to=huber@alum.wpi.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).