Gnus development mailing list
 help / color / mirror / Atom feed
From: Charles Philip Chan <cpchan@bell.net>
To: ding@gnus.org
Subject: Re: Mutt/Gnus hybrid for mail?
Date: Tue, 09 Dec 2014 16:20:57 -0500	[thread overview]
Message-ID: <87mw6wjz9i.fsf@karnak.MagnumOpus.khem> (raw)
In-Reply-To: <m2zjawc2ot.fsf@PFDStudio-Air.home>

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

On 9 Dec 2014, pfd@pfdstudio.com wrote:

> For me, Summary only shows the unread messages, and not even the rest
> of the threads they belong to (unless I type 'A T').

For me, I have Gnus set to see unread/ticked article and threads that
have unread and ticked articles. I have

   1. "gnus-fetch-old-headers" set to "some".
   2. "gnus-build-sparse-threads" set to "some".
   
It is much cleaner this way, since it is not cluttered with articles of
no interest. If I want to see old read one, I just use "/o".

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

I do use imap- a local Dovecot server.

> The 'l' command in mutt is not search, it's limit ... it limits the
> display to messages matching some criteria. Admittedly I haven't
> searched exhaustively for gnus features to mimic this, but I didn't
> see any obvious ones. Of course, as I said, since only unread messages
> show up in the Summary, this is not very useful in gnus.

In Gnus "/" is "limited to". It is very powerful:

   https://www.gnu.org/software/emacs/manual/html_node/gnus/Limiting.html



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 180 bytes --]

  parent reply	other threads:[~2014-12-09 21: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
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 [this message]
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=87mw6wjz9i.fsf@karnak.MagnumOpus.khem \
    --to=cpchan@bell.net \
    --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).