Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Standard way to use Gnus?
Date: Wed, 18 Mar 2015 20:59:11 +0100	[thread overview]
Message-ID: <87lhiuvzzk.fsf@debian.uxu> (raw)
In-Reply-To: <86619zgu9f.fsf@gmail.com>

David Masterson <dsmasterson@gmail.com> writes:

> I'm sure everyone has there own preferences on how
> to use Gnus -- that's the essense of Emacs, after
> all. However, it's always instructive to learn from
> others and find new methods of using such a powerful
> tool. I've been around Emacs & Gnus for more 30
> years (yes, I believe I used GNUS when it was
> written for TECO/Emacs), but I was never an expert
> in its usage. I still tend to just basically C-n &
> Space through the Summary buffer to read what I'm
> interested in and never really sat down to figure
> out the more advanced tools in Gnus.
>
> I'm now a little more curious. The Gnus manual in
> Emacs is written as a reference manual and covers a
> lot of complicated topics, but not in a manner of
> taking the novice to an expert level step by step.
> I'm looking for more on why each of the pieces of
> Gnus exist and examples of why I might want to use
> them. Is there such a manual around somewhere?

I don't know, but I would like to read it, if you find
it.

Generally though it is better to put the question like
this: what would you like to do? Or: what are you
doing, that you would like to do in another way? what
are you doing that you don't want to do? etc.

If you just want to be a more advanced user all over
the board, then indeed the reference manual should
keep you busy years to come :)

-- 
underground experts united

  reply	other threads:[~2015-03-18 19:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 21:59 David Masterson
2015-03-18 19:59 ` Emanuel Berg [this message]
     [not found] ` <zfudnUkDnvD5lZbInZ2dnUU7-LudnZ2d@supernews.com>
2015-03-19 18:40   ` Non Gnuser
2015-03-19 22:13     ` Adam Sjøgren
     [not found]     ` <mailman.2344.1426803317.31049.info-gnus-english@gnu.org>
2015-03-19 23:22       ` Emanuel Berg
2015-03-20  6:23         ` Adam Sjøgren
2015-03-20 21:12         ` interface to KILL file (was: Re: Standard way to use Gnus?) Emanuel Berg
2015-03-23 16:28       ` Standard way to use Gnus? Non Gnuser
2015-03-19 23:14 ` Jeffrey DeLeo
2015-03-20  7:05 ` Glyn Millington
     [not found] ` <mailman.2362.1426837049.31049.info-gnus-english@gnu.org>
2015-03-20 23:18   ` David Masterson
2015-03-21  7:33     ` Glyn Millington
     [not found]     ` <mailman.2465.1426963087.31049.info-gnus-english@gnu.org>
2015-03-22 23:12       ` David Masterson

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=87lhiuvzzk.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).