Gnus development mailing list
 help / color / mirror / Atom feed
From: Sten Drescher <dreschs@mpd.tandem.com>
Cc: jvinson@cheux.ecs.umass.edu (Jack Vinson)
Subject: Re: separating reading new mail and news
Date: Wed, 29 Nov 1995 15:26:37 -0600 (CST)	[thread overview]
Message-ID: <199511292126.PAA07115@galil.austnsc.tandem.com> (raw)
In-Reply-To: jvinson@cheux.ecs.umass.edu's message of 29 Nov 1995 14:49:17 -0500

jvinson@cheux.ecs.umass.edu (Jack Vinson) said:

>>>>>> "SK" == Saileshwar Krishnamurthy <krish@cs.purdue.edu> writes:
SK> It'll be nice if the fuctions for reading mail and news were
SK> separated instead of one group-get-new-news.

JV> No, just keep your mail groups at a lower level than your news
JV> groups.

	This is great, unless you have some news groups (which you don't want
to check) which are normally more important than some mail groups.  What
I do is "F" - gnus-find-new-newsgroups, which causes nnml to read my
procmail-generated spool files in order to discover if there are any new
groups (which, by the way, is a really neat thing - I don't have to
manually create nnml groups, it automagically creates them), then "2 g"
to update the article counts for the high-priority mail groups.  I'm
only guessing that this sequence would empty the mail spool if you are
letting Gnus split your mail for you, though.

-- 
#include <disclaimer.h>				/* Sten Drescher */
To get my PGP public key, send me email with your public key and
	Subject: PGP key exchange
Key fingerprint =  90 5F 1D FD A6 7C 84 5E  A9 D3 90 16 B2 44 C4 F3


      reply	other threads:[~1995-11-29 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-11-29 18:11 Saileshwar Krishnamurthy
1995-11-29 19:49 ` Jack Vinson
1995-11-29 21:26   ` Sten Drescher [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=199511292126.PAA07115@galil.austnsc.tandem.com \
    --to=dreschs@mpd.tandem.com \
    --cc=jvinson@cheux.ecs.umass.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).