Gnus development mailing list
 help / color / mirror / Atom feed
From: Peter Davis <pfd@pfdstudio.com>
To: "Peter Münster" <pmlists@free.fr>
Cc: ding@gnus.org
Subject: Re: Mutt/Gnus hybrid for mail?
Date: Mon, 08 Dec 2014 17:47:00 -0500	[thread overview]
Message-ID: <m2oarddajf.fsf@PFDStudio-Air.home> (raw)
In-Reply-To: <87egs952jy.fsf@micropit.roche-blanche.homenet.org> ("Peter \=\?utf-8\?Q\?M\=C3\=BCnster\=22's\?\= message of "Mon, 08 Dec 2014 21:06:41 +0100")

Peter Münster <pmlists@free.fr> writes:

> On Mon, Dec 08 2014, Peter Davis wrote:
>
>> For email, I like some things about mutt,
>
> Hi,
>
> What things?

Most significantly, since I only use mutt or gnus for email, I find mutt
more intuitive, since its commands, etc. were designed for email. "Delete"
instead of "Expire", etc. (BTW, I'm using both with Fastmail.fm IMAP.)

Also, when I delete/expire a message, mutt automatically displays the
next unread message in the folder. Gnus requires another keystroke. (Not
a big deal, but annoying.)

I have not managed to get gnus to display previously read messages in a
thread automatically, though I've messed around with 
(setq gnus-fetch-old-headers t). I gather this is inconsistent on IMAP
servers, and slow.

I realize I could customize gnus to behave exactly the way I want, but
I'm not a much of a lisper, so it would take me a fair bit of
effort. Anyway, customatizations are unlikely to improve
performance. Mutt seems faster at downloading messages, etc.

I'm certainly open to suggestions on how to improve any of these.

Thanks,
-pd



  reply	other threads:[~2014-12-08 22:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 13:20 Peter Davis
2014-12-08 20:06 ` Peter Münster
2014-12-08 22:47   ` Peter Davis [this message]
2014-12-08 23:25     ` Peter Münster
2014-12-09  0:15       ` Peter Davis
2014-12-09  0:51       ` Peter Davis
2014-12-09  8:00         ` Peter Münster
2014-12-09  0:20     ` Jorge A. Alfaro-Murillo
2014-12-09  0:47       ` Peter Davis
2014-12-09  3:57     ` Charles Philip Chan
2014-12-09  4:04       ` Charles Philip Chan
2014-12-09 10:46     ` Eric S Fraga
2014-12-09 12:49       ` Peter Davis
2014-12-09 14:10         ` Eric S Fraga
2014-12-09 14:34           ` Peter Davis
2014-12-09 16:15             ` Eric S Fraga
2014-12-09 17:42               ` Peter Davis
2014-12-09 18:26                 ` Adam Sjøgren
2014-12-09 19:56                   ` Peter Davis
2014-12-09 20:16                     ` Adam Sjøgren
2014-12-09 21:21                       ` Peter Münster
2014-12-09 21:20             ` Charles Philip Chan
2014-12-09 22:46               ` Peter Davis
2014-12-10  0:19                 ` Charles Philip Chan
2014-12-10  0:25                   ` Peter Davis
2014-12-10  1:35                     ` Charles Philip Chan
2014-12-10  2:01                       ` Peter Davis

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=m2oarddajf.fsf@PFDStudio-Air.home \
    --to=pfd@pfdstudio.com \
    --cc=ding@gnus.org \
    --cc=pmlists@free.fr \
    /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).