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: adive to a gnus newbie
Date: Thu, 19 Jun 2014 04:43:01 +0200	[thread overview]
Message-ID: <87y4wthb62.fsf@debian.uxu> (raw)
In-Reply-To: <yre9ppi7po3r.fsf@sdf.lonestar.org>

Dennis Askey <mrascii@sdf.lonestar.org> writes:

>> The gnus document is complicated to me, maybe it is
>> because I am new to gnus.  Now I have the basic
>> setting myself, and read some tutorials.  I am
>> trying to read and understand gnus documents.  It
>> can be painful if you don't know what others talk
>> about gnus for beginners.  Thanks for reply.
>
> I had trouble understanding gnus for the longest time
> until I simply sat down and read the help group that
> gnus automatically shows when you first start it and
> then read section 6.3 Getting Mail in the gnus
> manual.  I used those sources to create a barebones
> ~/.gnus.el.

Yes, Gnus isn't that easy, I thought it was much more
difficult to get into than Emacs in general, which was
straightforward by comparison to my mind...

I hope I don't make anyone angry by saying this, but I
don't care much for reading tutorials. Or, put it this
way - tutorials (and books) come in at a later stage,
when you already have a functional understanding. This
will make for many unpleasant revelations when you find
out that your elaborate hacking can be replaced by
setting a single option (blushes)...

But as said, that is step to. Step one is: get the door
open, by forcing your leg between the door and the
panel. When it is open just a bit, you may turn and
twist your leg to a more comfortable position, and
start refining you methods. So:

1) Use it. For mails and for Usenet posts. Never use
anything else. No exceptions.

2) Learn one thing every day. May be a variable, a
shortcut, a term - whatever as tiny. In 365 days, you
will have acquire 365 such pieces of knowledge (except
for the leap years, when you are even more productive).

3) When you have learned on one such thing, relax, be
happy, and keep using it.

-- 
underground experts united:
http://user.it.uu.se/~embe8573

      reply	other threads:[~2014-06-19  2:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06  8:05 jenenliu
2014-03-07 12:55 ` Martin
2014-03-07 14:42   ` jenenliu
     [not found]   ` <mailman.16670.1394204722.10748.info-gnus-english@gnu.org>
2014-06-17 15:11     ` Dennis Askey
2014-06-19  2:43       ` Emanuel Berg [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=87y4wthb62.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).