From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: ding@gnus.org
Subject: Re: Mutt/Gnus hybrid for mail?
Date: Mon, 08 Dec 2014 19:20:29 -0500 [thread overview]
Message-ID: <87bnndsmgi.fsf@yale.edu> (raw)
In-Reply-To: <m2oarddajf.fsf@PFDStudio-Air.home>
Peter Davis writes:
> 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.)
If you use IMAP perhaps you should move the messages to the Trash
group instead of expiring them.
I think that expiring fits more to handling your email like news,
meaning, you only read what it is not read, and leave everything
in the server. You don't worry about deleting things and just for
space issues you expire things that are very old. Of course there
are things that require your attention later, and that you want to
keep showing as news. For those you use ticks (key "!").
> 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.)
You could assign a key to a function like this:
#+BEGIN_SRC emacs-lisp
(defun my-gnus-summary-delete-article ()
(interactive)
(gnus-summary-move-article nil "nnimap+Fastmail.fm:Trash")
(gnus-summary-next-unread-article))
#+END_SRC
"nnimap+Fastmai.fml:Trash" is just a guess, you should use
whatever your group is called.
> 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.
Maybe try setting
#+BEGIN_SRC emacs-lisp
(setq gnus-refer-thread-use-nnir t)
#+END_SRC
And then use "A T" when you need it. With 99% of the people using
a TOFU (Text Over, Fullquote Under) style, most of the time you do
not need to see the whole thread since it appears in the latest
email.
> Anyway, customatizations are unlikely to improve performance.
> Mutt seems faster at downloading messages, etc.
I would also like to hear about ways to improve performance.
Best,
--
Jorge.
next prev parent reply other threads:[~2014-12-09 0:20 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 [this message]
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=87bnndsmgi.fsf@yale.edu \
--to=jorge.alfaro-murillo@yale.edu \
--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).