unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: YUE Daian <sheepduke@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Question mail package
Date: Thu, 24 Oct 2019 21:27:01 +0800	[thread overview]
Message-ID: <87y2xai89m.fsf@home.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87tv7z5l10.fsf@bobnewell.net>

On 2019-10-23 09:17, Bob Newell <bobnewell@bobnewell.net> wrote:
>    IMHO it is a better idea to make your configurations evolve along with
>    your experience with Emacs, instead of trying to get everything "set"
>    before sailing.
>
> This is excellent advice and well worth noting. You don't have
> to eat the whole elephant at once. A minimal config for Gnus,
> as was presented elsewhere in this thread, is probably 30
> lines or so.
>
> It took me 10 years to get up to 1,000 lines ... that seems
> about right.
>
> -- 
> Bob Newell
> Honolulu, Hawai`i
> - Via Gnus/BBDB/Org/Emacs/Linux

To be honest I said it because I used to get everything "prepared"
before really using it. When I was in bachelor I spent all my spare time
within a week reading Emacs's documentation. I read almost everything.

It was not a good idea.

As for Gnus, I do not think 30 lines will give you a satisfying
experience compared with other alternatives. I tried. Maybe it was just
me.

But it has so many concepts related to good old new groups, instead of
mails. I do not think it is a good idea to recommend it to beginners.

Anyway, you have the choices.



  reply	other threads:[~2019-10-24 13:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 19:17 Question mail package Bob Newell
2019-10-24 13:27 ` YUE Daian [this message]
2019-10-24 22:20   ` VanL
2019-10-25 13:36   ` Filipp Gunbin
  -- strict thread matches above, loose matches on Subject: below --
2019-10-21 12:07 Ergus
2019-10-21 13:21 ` Teemu Likonen
2019-10-21 13:54 ` VanL
2019-10-21 14:05 ` YUE Daian
2019-10-22  7:26   ` Bob Newell
2019-10-22  7:36     ` YUE Daian
2019-10-22 11:50     ` Teemu Likonen
2020-03-30 20:56     ` Bruno Félix Rezende Ribeiro
2020-03-30 21:36       ` Eric Abrahamsen
2020-04-09  3:00         ` 황병희
2020-04-10  2:51         ` Bruno Félix Rezende Ribeiro
2020-03-31 11:10       ` Eric S Fraga
2020-04-08 21:00         ` Bruno Félix Rezende Ribeiro
2019-10-27 21:16   ` Jorge P. de Morais Neto
2019-10-28  7:00     ` Teemu Likonen
2019-11-10 10:03 ` 황병희

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2xai89m.fsf@home.i-did-not-set--mail-host-address--so-tickle-me \
    --to=sheepduke@gmail.com \
    --cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).