Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Kyle Sexton <ks@mocker.org>
Cc: ding@gnus.org
Subject: Re: Features that make you love Gnus?
Date: Fri, 21 Sep 2012 08:50:50 +0200	[thread overview]
Message-ID: <87mx0j6f91.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <CAP=acfzZ6DAKdvWuFk8A3-6=iL6vomOfn0H7TXhYwkDT5JRgEA@mail.gmail.com> (Kyle Sexton's message of "Thu, 20 Sep 2012 08:48:13 -0500")

Kyle Sexton <ks@mocker.org> writes:

> I've got Gnus setup to handle my work email and it works well, but I
> use it in the most basic way.  What cool features should I start
> checking out that makes you love Gnus?

Except for the cool features like scoring, threading, sane IMAP support,
good and fast searching with nnir, good integration with org-mode, two
rather simple things make me totally dependent on gnus:

1. gcc-self: I don't want to separate my mail in "received" and "sent".
   I want to see complete conversations!

   Frankly, yesterday at my father's computer I've seen that Firefox now
   has a "Keep replies in current folder" feature.  But of course it's
   not as flexible as gnus gcc-self.

2. I really, really hate receiving badly formatted mail.  Gnus washing
   commands help a bit sometimes, but more importantly, message-mode is
   just awesome for writing perfectly formatted plain-text mail.  If you
   write me some totally bogus, messed-up Outlook salad, you'll get a
   perfectly formatted reply where even your own text looks good (and of
   course the request to use some sane email program).

Ah, and not to forget, there are all those little niceties like
gravatars, notifications and google contacts integration that have
changed it from a bit baroque to well-integrated on the free desktop and
so Web 2.0-y.

Bye,
Tassilo



  parent reply	other threads:[~2012-09-21  6:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 13:48 Kyle Sexton
2012-09-20 22:48 ` Oleksandr Gavenko
2012-09-21  6:35   ` Tassilo Horn
2012-09-23 21:34     ` Oleksandr Gavenko
2012-09-24  6:47       ` Tassilo Horn
2012-09-21  1:11 ` Mark Simpson
2012-09-23 21:38   ` Oleksandr Gavenko
2012-09-23 23:59     ` Mark Simpson
2012-09-21  6:50 ` Tassilo Horn [this message]
2012-09-21 13:16   ` Erik Colson
2012-09-21 18:23   ` Sivaram Neelakantan
2012-09-21 18:56     ` Tassilo Horn
2012-09-23 21:42   ` Oleksandr Gavenko
2012-09-24  6:52     ` Tassilo Horn
2012-09-24  8:22       ` Andreas Schwab
2012-09-21 13:23 ` Julien Danjou
2012-09-22 17:39 ` Adam Sjøgren
2012-09-25 13:20   ` Malcolm Purvis
2012-09-24  7:26 ` Eric Abrahamsen
2012-09-24 12:30   ` Adam Sjøgren
2012-09-26  6:26     ` 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=87mx0j6f91.fsf@thinkpad.tsdh.de \
    --to=tsdh@gnu.org \
    --cc=ding@gnus.org \
    --cc=ks@mocker.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).