Gnus development mailing list
 help / color / mirror / Atom feed
From: Steven L Baur <steve@miranova.com>
Subject: Re: mail
Date: 17 May 1996 17:13:20 -0700	[thread overview]
Message-ID: <m2k9yasusf.fsf@deanna.miranova.com> (raw)
In-Reply-To: michael lamoureux's message of 17 May 1996 12:48:00 -0700

>>>>> "michael" == michael lamoureux <lamour@engin.umich.edu> writes:

michael> [problem description deleted -- mjl]

michael> I solved it.  Basically, I set up an nnml secondary-select
michael> method, and couldn't find some of the groups when the mail
michael> came in.  I went through a LOT of pain to find them.
michael> Shouldn't they just automatically show up the first time mail
michael> arrives in the groups?  My worry is that I won't notice when
michael> I get mail to one of those groups I set up for people I don't
michael> get mail from very often.

This can be a problem.  I don't have good solution either.  Adding
groups for me is a manual process.

I solve it by creating the group with G m and positioning it to the
location (position in *Group* buffer, or Topic) I want it to be.
Setting the level to 2 or 1 if it is a group which will have mail
automatically put in it.  After I'm sure what the headers look like
for messages I want put in the group I will add the appropriate recipe
to my .procmailrc.  This works only if the set of groups is fairly
static.

I've been experimenting with various color schemes in the
gnus-group-highlight variable (a very nifty September Gnus feature!),
but haven't found something I really like yet.  The closest has been
to vary the shade depending on subscription level.

michael> Also, I can't get supercite to work even though I have this set:

	http://www.miranova.com/~steve/gnus-faq.html#Q2_12

Regards,
-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.


  reply	other threads:[~1996-05-18  0:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-17 19:48 mail michael lamoureux
1996-05-18  0:13 ` Steven L Baur [this message]
1996-05-20 21:25   ` mail michael lamoureux
1996-05-20 22:32     ` mail Lars Magne Ingebrigtsen
1996-05-21  7:29       ` mail Ketil Z Malde
1996-05-21 13:55         ` mail Lars Magne Ingebrigtsen
1996-05-21 16:57           ` mail Hallvard B Furuseth
1996-05-21 17:43             ` mail Lars Magne Ingebrigtsen
1996-05-21 17:54           ` mail michael lamoureux
1996-05-21 18:47         ` mail Mark Eichin
1996-05-21 22:33           ` mail Steven L Baur
1996-05-20 22:34     ` mail Danny Siu
1996-05-18  6:48 ` mail Lars Magne Ingebrigtsen
1996-05-18 16:38   ` mail Steven L Baur
1996-05-19  8:14     ` mail Lars Magne Ingebrigtsen

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=m2k9yasusf.fsf@deanna.miranova.com \
    --to=steve@miranova.com \
    /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).