From: Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de>
Cc: ding@hpc.uh.edu
Subject: Re: gnus email resources
Date: 24 Aug 1998 11:14:16 +0200 [thread overview]
Message-ID: <vafww7y68t3.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: Phil Humpherys's message of "22 Aug 1998 01:09:29 -0600"
>>>>> Phil Humpherys <phumpherys@utah-inter.net> writes:
> I'm finding the FAQ and manual for gnus just enough to get email
> going in gnus, but not nearly enough to really tweak it the way I
> like. Could someone point me in the right direction for some
> other helps?
Uhm, read the manual some more? You might also want to ask some
specific questions in the Gnus newsgroup or on this mailing list, but
many issues are covered in the manual.
My suggestion is: print out the manual and make it your bedtime
reading for a while.
kai
--
OOP: object oriented programming; OOPS: object oriented mistakes
prev parent reply other threads:[~1998-08-24 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-22 7:09 Phil Humpherys
1998-08-24 9:14 ` Kai Grossjohann [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=vafww7y68t3.fsf@ramses.cs.uni-dortmund.de \
--to=grossjohann@amaunet.cs.uni-dortmund.de \
--cc=ding@hpc.uh.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).