Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Frank Schmitt <usereplyto@Frank-Schmitt.net>
Subject: Re: Gnus FAQ good for printing?
Date: Sun, 29 Dec 2002 16:58:30 +0100	[thread overview]
Message-ID: <adiog6l5.fsf@hschmi22.userfqdn.rz-online.de> (raw)
In-Reply-To: <iloverobin.87hecxdrbt.fsf@news.socha.net>

"Robin S. Socha" <robin@socha.net> writes:

> * Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
>> Don Saklad <dsaklad@nestle.ai.mit.edu> writes:
>
>>> A glossary of technical phraseology and jargon with links for
>>> elaborations on the definitions would be a good thing to include
>>> in such an faq.
>> 
>> Yes, noted.
>
> What for? Those are *not* frequently asked questions. All of them are
> explained in <http://www.geocities.com/nnqweb/> and links therein. It's
> a Gnus FAQ, not an introduction to newsreaders in general. Furthermore,
> <http://quimby.gnus.org/notes/notes.html> appears to be fairly
> comprehensive.

My idea was:
-------->------------>-------
Glossary:
When I say Emacs in this FAQ I mean either FSF Emacs or XEmacs. When I
say message I mean either posting to Usenet or mail, whereas
article means posting to Usenet...

About 10-20 lines explaining things I use in the FAQ which people might
stumble about while reading the FAQ. More examples could be backend or
select-method.
-------->------------>-------

I don't really know if this matches Don's idea as I didn't really
understood what he wrote, but I'd think this would be useful.

If you thing this doesn't fit in a FAQ, then I'll perhaps call it LQAWTT
(List of Questions and Answers With Tutorial Touch) :-)

-- 
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.


       reply	other threads:[~2002-12-29 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <86k7hvb6un.fsf@zeus.knighten.org>
     [not found] ` <bs36v65d.fsf@hschmi22.userfqdn.rz-online.de>
     [not found]   ` <y447kdt5gsc.fsf@nestle.ai.mit.edu>
     [not found]     ` <d6nlf8ye.fsf@hschmi22.userfqdn.rz-online.de>
     [not found]       ` <iloverobin.87hecxdrbt.fsf@news.socha.net>
2002-12-29 15:58         ` Frank Schmitt [this message]
     [not found]           ` <6865tch9gt.fsf@fencepost.gnu.org>
2002-12-30  0:34             ` Bijan Soleymani,,,

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=adiog6l5.fsf@hschmi22.userfqdn.rz-online.de \
    --to=usereplyto@frank-schmitt.net \
    --cc=replies@Frank-Schmitt.net \
    /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).