Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: prad <prad@towardsfreedom.com>
To: info-gnus-english@gnu.org
Subject: a strategy for reading newsgroups
Date: Tue, 28 Dec 2010 13:45:35 -0800	[thread overview]
Message-ID: <87pqsla7wg.fsf@towardsfreedom.com> (raw)

do people have efficient strategies for handling newsgroups?
are there any links that pertain specifically to gnus?

here is one issue for instance that is bothering me and haven't found a
solution for in the excellent and humorously written manual, yet.

when i go into a newsgroup there may be 9999 posts. they are all unread
and i'm asked how many do i want to download. so i say 99 and read a few
and may be reply to a few or post some of my own.

now i go back to the group and it would be nice to see new replies to my
efforts or the threads i was involved in. however, i'm asked how many do
i want to download and i see the new items again some of which are of
course the ones i'm interested in. 

i suppose the marking and prioritizing threads can assist here, but i'm
also thinking that if i could mark an entire group as read, then i'd
only get new posts when i go in, so that's a lot less to sift
through. (i can mark a group with #, but haven't figured out how to mark
everything within it as being read). possibly, this may not be a good
idea either or there may be more intelligent ways of doing things.

is there some sort of gnus for dummies that is available?

--
In friendship,
prad

                                      ... with you on your journey
Towards Freedom
http://www.towardsfreedom.com (website)
Information, Inspiration, Imagination - truly a site for soaring I's

             reply	other threads:[~2010-12-28 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28 21:45 prad [this message]
2010-12-31  1:40 ` prad
     [not found] <mailman.8.1293572714.3661.info-gnus-english@gnu.org>
2010-12-28 21:56 ` Massimo Gengarelli
2010-12-29  1:16   ` prad
2010-12-29 10:49   ` Tassilo Horn

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=87pqsla7wg.fsf@towardsfreedom.com \
    --to=prad@towardsfreedom.com \
    --cc=info-gnus-english@gnu.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;
as well as URLs for NNTP newsgroup(s).