From: Alberto Luaces <aluaces@udc.es>
To: ding@gnus.org
Subject: Re: gmail setup
Date: Fri, 10 Apr 2020 18:56:05 +0200 [thread overview]
Message-ID: <87eesvuvoa.fsf@eps142.cdf.udc.es> (raw)
In-Reply-To: <875zea7nfp.fsf@emailmessageidheader.nil>
Bob Newell writes:
> But then, if the complexity puts you off, there are indeed
> other viable Emacs-based options like mu4e and others, and
> that's as it should be.
Bob, I agree with you in everything you said except this: mu4e is not
simpler to configure, I wouldn't recommend it to a newbie. It has many
good things, but setting it is as complex as setting nnmaildir.
Anecdotally, I personally find posting styles to be easier to setup than
mu4e's contexts.
I think that the complexity comparison comes from the fact that gnus can
do much more things than the other MUAs, but if you restrict the
comparison to the common ground they all share (being it mu4e, notmuch
or even mutt), they are not that different.
--
Alberto
next prev parent reply other threads:[~2020-04-10 16:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 14:33 how to forward a message that contains attachment Uwe Brauer
2020-04-04 14:54 ` Eric S Fraga
2020-04-04 18:57 ` Uwe Brauer
2020-04-05 2:00 ` Bob Newell
2020-04-05 6:07 ` Uwe Brauer
2020-04-05 19:31 ` Bob Newell
2020-04-05 13:18 ` Eric S Fraga
2020-04-05 17:11 ` Uwe Brauer
2020-04-05 17:37 ` Adam Sjøgren
2020-04-05 21:25 ` dick.r.chiang
2020-04-06 10:19 ` gmail setup (was: how to forward a message that contains attachment) Alberto Luaces
2020-04-07 16:42 ` gmail setup dick.r.chiang
2020-04-07 17:46 ` Alberto Luaces
2020-04-07 18:19 ` dick.r.chiang
2020-04-07 18:35 ` Alberto Luaces
2020-04-08 1:53 ` Bob Newell
2020-04-10 16:56 ` Alberto Luaces [this message]
2020-04-06 10:19 ` how to forward a message that contains attachment Uwe Brauer
2020-04-06 10:26 ` Uwe Brauer
2020-04-07 17:03 ` Adam Sjøgren
2020-04-06 11:36 ` Uwe Brauer
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=87eesvuvoa.fsf@eps142.cdf.udc.es \
--to=aluaces@udc.es \
--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).