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: Tue, 09 Dec 2014 07:49:21 -0500	[thread overview]
Message-ID: <m24mt5c7ji.fsf@PFDStudio-Air.home> (raw)
In-Reply-To: <8761dl3xth.fsf@pinto.chemeng.ucl.ac.uk> (Eric S. Fraga's message of "Tue, 9 Dec 2014 10:46:34 +0000")


Thanks very much for all the excellent suggestions. However, I think
perhaps I need to clarify what I'm missing.

1) Deleting

In mutt, when I'm looking at a message with what mutt calls the "index"
at the top, and "pager" at the bottom, analagous to gnus' Summary and
Article buffers, I can, with a single keystroke

1) move to and read the next message, or
2) move to and read the next unread message, or
3) delete the current message, and move to and read the next message.

I want to be able to either save or delete (expire) a message and open
the next one automatically. Frankly, it seems weird to me that gnus
moves the cursor in the Summary buffer to the next message, but still
displays the message I just expired in the Article buffer.

If I'm on the last message in the mutt index and I delete that, mutt
simply closes the 'pager' view and just displays the index view for the
whole screen.

2) Opening a group/mailbox

In mutt, when I open a mailbox (group), I see an index of all the
messages in the mailbox, with the cursor positioned at the first unread,
if any. I like that, but I'd settle for seeing all of the threads
containing any unread messages. As I understand it,
gnus-fetch-old-headers is supposed to do that, but I haven't found a way
to make it work, at least with Fastmail.fm IMAP.

For extra credit, in mutt's index (Summar) view, I can very easily
filter the list of messages with a few keystrokes. For instance, if I
type lpfd, I'll see just a list of messages whose headers contain
"pfd". Of course, this is not especially useful in gnus since the
Summary buffer doesn't show me a long list of earlier messages, but if I
could make that happen, it would be very useful.

Thanks again!

-pd



  reply	other threads:[~2014-12-09 12:49 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
2014-12-09 12:49       ` Peter Davis [this message]
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=m24mt5c7ji.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).