From: "Peter Münster" <pmlists@free.fr>
To: ding@gnus.org
Subject: Re: Mutt/Gnus hybrid for mail?
Date: Tue, 09 Dec 2014 00:25:59 +0100 [thread overview]
Message-ID: <87r3w93erc.fsf@micropit.roche-blanche.homenet.org> (raw)
In-Reply-To: <m2oarddajf.fsf@PFDStudio-Air.home>
On Mon, Dec 08 2014, Peter Davis wrote:
> 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.)
This sets the expire mark with the "d" key and goes to next message:
--8<---------------cut here---------------start------------->8---
(defun pm/alter-summary-map ()
(local-set-key "d" [?M ?M ?e ?e down]))
(defun pm/alter-article-map ()
(local-set-key "d" "MMeen"))
(add-hook 'gnus-summary-mode-hook 'pm/alter-summary-map)
(add-hook 'gnus-article-mode-hook 'pm/alter-article-map)
--8<---------------cut here---------------end--------------->8---
> I have not managed to get gnus to display previously read messages in a
> thread automatically,
You mean, display all messages of a thread, when it has at least one new
message? I'm sure, that this is possible and you would get a solution
here...
If you want it with a key-press: it's "A T".
> 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.
Elisp is very useful, not only in Gnus. And you can get help here.
> Anyway, customatizations are unlikely to improve performance. Mutt
> seems faster at downloading messages, etc.
Perhaps. But the Mutt-macros are *very* limited and when you want to
display something else than plain text, Mutt needs external programs,
where the key-bindings are completely different and you can't control Mutt
anymore...
After having switched from Mutt to Gnus, I've just thought:
"Why haven't I done that earlier...?!"
I'm sure, that you'll spend more time integrating Mutt into Emacs the
way you like, than reading the Gnus manual.
--
Peter
next prev parent reply other threads:[~2014-12-08 23:25 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 [this message]
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=87r3w93erc.fsf@micropit.roche-blanche.homenet.org \
--to=pmlists@free.fr \
--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).