From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: "Gnus" in other editors/IDEs
Date: Mon, 27 May 2019 15:18:14 -0700 [thread overview]
Message-ID: <87lfyra6e1.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 865zpvd0ps.fsf_-_@zoho.eu
Emanuel Berg via help-gnu-emacs <help-gnu-emacs@gnu.org> writes:
> Tomas Nordin wrote:
>
>>> I got it figured out a few days ago. But for
>>> now I may have to go slow and learn how to
>>> configure gnus while using the webmail
>>> interface as I go. Doing (setq
>>> gnus-select-method '(nnimap "posteo.de"))
>>> was the answer I needed! Everything else can
>>> probably be learned by RTFM
>>
>> Alright! Good luck with the Gnus stuff, it
>> seems to be THE thing for some people.
>
> You better believe it!
>
> With all the bad rep Emacs has got lately -
> I mean, it can't even handle cpp projects with
> a few million lines OOTB - let me ask, can them
> other editors and IDEs, that are better, and
> have a less steep learning curve than Emacs,
> can _they_ do their "Gnuses" and are they
> really better than ours as well? Allow me
> to be - doubtful!
>
> Like the saying goes, Gnus is to Emacs users
> what Emacs is to other users :)
>
> Gnus is actually so good, it is
> counter-productive to many people.
Amen.
prev parent reply other threads:[~2019-05-27 22:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 5:50 Newbie with Gnus and posteo email setup oury.dustin
2019-05-23 16:06 ` Eric Abrahamsen
2019-05-23 17:30 ` Nick Dokos
2019-05-23 17:48 ` Eric Abrahamsen
2019-05-24 14:29 ` Nick Dokos
2019-05-24 18:02 ` Eric Abrahamsen
2019-05-23 21:26 ` Tomas Nordin
[not found] ` <a368152ed065e6faf513cf684f90ed98@posteo.net>
2019-05-25 15:31 ` Tomas Nordin
2019-05-27 21:52 ` "Gnus" in other editors/IDEs (was: Re: Newbie with Gnus and posteo email setup) Emanuel Berg via help-gnu-emacs
2019-05-27 22:18 ` Eric Abrahamsen [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
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=87lfyra6e1.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).