Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Joost Diepenmaat <joost@zeekat.nl>
To: info-gnus-english@gnu.org
Subject: Re: learning gnus
Date: Sun, 30 Dec 2007 23:21:20 +0100	[thread overview]
Message-ID: <87r6h3x1r3.fsf@zeekat.nl> (raw)
In-Reply-To: <u8x3brhmo.fsf@tiscali.co.uk>

David Rod <angel_ov_north@tiscali.co.uk> writes:

> I believe that there used to be a tutorial about gnus at some website,
> but this is no longer on the web.
>
> There appears to be a huge gap in the book market for gnus because there
> are not any books about gnus ever written.  Such a book would assume
> that another book about an introduction to emacs had already been read.  
>
> I know vaguely that setq will change a variable but I really want a
> cookbook because if I start messing around with things I will break
> things without any knowledge about what I am breaking.
>
> Reading the info manual is a 2 week task!
> Thanks for advice.  Will try (blindly). 

(setq) and lots of other stuff used in configuring emacs and gnus are
emacs-lisp functions or macros. If you're familar with any lisp variant
translating to and from emacs lisp isn't very hard. If you're not
familiar with lisp, and mainly interested in emacs/gnus,

<http://www.gnu.org/software/emacs/emacs-lisp-intro/html_mono/emacs-lisp-intro.html>

should get you started. Chapter 1 should tell you almost all you need to
do minimal configuration.

Joost.

  parent reply	other threads:[~2007-12-30 22:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26 22:35 David Rod
2007-12-27  9:38 ` Tassilo Horn
     [not found] ` <mailman.5427.1198748349.18990.info-gnus-english@gnu.org>
2007-12-30 21:34   ` David Rod
2007-12-30 22:06     ` Glyn Millington
2007-12-30 22:21     ` Joost Diepenmaat [this message]
2007-12-30 23:04       ` Joost Diepenmaat
2007-12-31  0:53     ` Leo
2008-02-06 13:05   ` Sébastien Vauban

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=87r6h3x1r3.fsf@zeekat.nl \
    --to=joost@zeekat.nl \
    --cc=info-gnus-english@gnu.org \
    /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).