From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: Mutt/Gnus hybrid for mail?
Date: Tue, 9 Dec 2014 10:46:34 +0000 [thread overview]
Message-ID: <8761dl3xth.fsf@pinto.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <m2oarddajf.fsf@PFDStudio-Air.home>
On Monday, 8 Dec 2014 at 17:47, Peter Davis wrote:
[...]
> 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.)
As others have said, you can bind keys to whatever you want. For
instance,
#+begin_src emacs-lisp
(defun esf/alter-summary-map ()
(local-set-key "d" 'gnus-summary-delete-article)
(local-set-key "e" 'gnus-summary-mark-as-expirable)
(local-set-key "u" 'gnus-summary-put-mark-as-unread)
(local-set-key "w" 'gnus-article-fill-long-lines)
)
(add-hook 'gnus-summary-mode-hook 'esf/alter-summary-map)
#+end_src
> 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.)
Gnus displays the next article for me if I am displaying an
article and hit "n", " " or "e". Otherwise not. If I am not displaying
an article, "n" and " " display the next article.
> 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 use the agent and, in combination with settings gnus-fetch-old-headers
to t, I get the ancestors of any email shown in the summary window. I
don't know if the agent is key here but it probably helps with speed.
> 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.
Mutt *is* faster but *I* am faster with gnus than with mutt in terms of
productivity. YMMV, of course :) I used mutt for years before
switching to gnus maybe 8 years ago now and haven't looked back.
HTH,
eric
--
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 24.4.1 + Ma Gnus v0.12 + evil-git-d432ec2
: BBDB version 3.1.2 (2014-04-27 15:05:20 -0500)
next prev parent reply other threads:[~2014-12-09 10:46 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
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 [this message]
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=8761dl3xth.fsf@pinto.chemeng.ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).