Gnus development mailing list
 help / color / mirror / Atom feed
From: Peter Davis <pfd@pfdstudio.com>
To: ding@gnus.org
Subject: Re: Mutt/Gnus hybrid for mail?
Date: Mon, 08 Dec 2014 19:47:14 -0500	[thread overview]
Message-ID: <m2d27td4z1.fsf@PFDStudio-Air.home> (raw)
In-Reply-To: <87bnndsmgi.fsf@yale.edu> (Jorge A. Alfaro-Murillo's message of "Mon, 08 Dec 2014 19:20:29 -0500")

jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) writes:

> 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 do have the expiry target set to INBOX.Trash

>
>> 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.
>

Worth a try. Does this actually display the next unread message, or just
move the cursor to it?

>> 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.
>  

Using 'A T' works, but I don't want to do that. I want all messages in
any threads with unread articles to just be there when I enter the group.

>> 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.

Yes, I'm always glad to learn ways to make gnus faster or more usable.

Thank you.

-pd



  reply	other threads:[~2014-12-09  0: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
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 [this message]
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=m2d27td4z1.fsf@PFDStudio-Air.home \
    --to=pfd@pfdstudio.com \
    --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).