Gnus development mailing list
 help / color / mirror / Atom feed
From: Sivaram Neelakantan <nsivaram.net@gmail.com>
To: ding@gnus.org
Subject: Re: Gnus work
Date: Thu, 05 Oct 2017 22:07:35 +0530	[thread overview]
Message-ID: <krpqx3376xh7ow.fsf@gmail.com> (raw)
In-Reply-To: <87wp4aa86j.fsf@ericabrahamsen.net>

On Wed, Oct 04 2017,Eric Abrahamsen wrote:


[snipped 45 lines]

>
> The current Gnus manual explicitly says that it does not aim to provide
> a tutorial. Users, however, are obviously in desperate need of a
> tutorial. Most recently, I think Adam Sjøgren (was it Adam?) posted an
> online version of his work-in-progress tutorial, and I know there are a
> few others -- why not incorporate these into the manual? A "getting
> started" tutorial, and a "moving your existing mail into Gnus" tutorial.
> I had a hell of a time migrating to Gnus whenever that was, lo these
> many years ago, though of course I took no notes and immediately after
> couldn't remember what was so difficult about it. :(

Same here.  A long time ago, someone posted that they didn't know
where to get started using gnus and I think Jason Rumney(sp?) posted
something along the lines of "do this, this and this and you're
good".Worked for me and promptly forgot what my fears were(to help
others and take more notes)

I can't find the post by Jason too now.  Pretty sure was either here
or help-Emacs-Windows list. or gnu.Emacs.help 

[snipped 8 lines]



sivaram
-- 




  parent reply	other threads:[~2017-10-05 16:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 18:32 Eric Abrahamsen
2017-10-04 18:43 ` Emanuel Berg
2017-10-04 18:53   ` Eric Abrahamsen
2017-10-04 21:07     ` Emanuel Berg
2017-10-04 21:09 ` Tim Landscheidt
2017-10-04 21:56   ` Eric Abrahamsen
2017-10-05  5:19     ` Adam Sjøgren
2017-10-05 17:35       ` Eric Abrahamsen
2017-10-05 17:51         ` Adam Sjøgren
2017-10-05 20:10           ` Eric Abrahamsen
2017-10-05 16:37     ` Sivaram Neelakantan [this message]
2017-10-05  6:53 ` Julien Danjou
2017-10-05 13:31 ` Lars Ingebrigtsen
2017-10-05 18:12   ` Eric Abrahamsen

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=krpqx3376xh7ow.fsf@gmail.com \
    --to=nsivaram.net@gmail.com \
    --cc=ding@gnus.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).