From: "Edward J. Sabol" <sabol@thuban.gsfc.nasa.gov>
Subject: Re: Sgnus 0.32 NEWS file
Date: Tue, 30 Jan 1996 15:34:07 -0500 [thread overview]
Message-ID: <199601302034.PAA28202@thuban.gsfc.nasa.gov> (raw)
In-Reply-To: <199601301754.AA233344472@chroma.ece.ucdavis.edu> (message from Wes Hardaker on Tue, 30 Jan 1996 09:54:31 -0800)
Excerpts from mail: (30-Jan-96) Re: Sgnus 0.32 NEWS file by Wes Hardaker
> I think that Per's and yours should be combined (or cross checked for
> things that aren't in one of them). I like that Per's had the "getting
> started with this feature" hints in it. You should consider adopting
> his :-)
I have to agree. Things like "Enable with (setq 'gnus-use-trees t)" and "Type
`t' to enable, and `T C-h' to get a list of commands" are very helpful. Per's
also seemed to be arranged in a more hierarchical fashion which made reading
it easier.
Later,
Ed "I'm still stuck with Emacs 19.28" Sabol
next prev parent reply other threads:[~1996-01-30 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-29 16:20 Per Abrahamsen
1996-01-30 16:29 ` Lars Magne Ingebrigtsen
1996-01-30 17:54 ` Wes Hardaker
1996-01-30 20:34 ` Edward J. Sabol [this message]
1996-01-31 15:18 ` Dave Goldberg
1996-01-31 20:46 ` 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=199601302034.PAA28202@thuban.gsfc.nasa.gov \
--to=sabol@thuban.gsfc.nasa.gov \
/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).