From: Rainer M Krug <Rainer@krugs.de>
To: ding@gnus.org
Subject: Re: Folding in article window?
Date: Mon, 03 Jun 2013 16:04:15 +0200 [thread overview]
Message-ID: <87d2s3qoio.fsf@krugs.de> (raw)
In-Reply-To: <877gibjphg.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Rainer M Krug <Rainer@krugs.de> writes:
>
>
> [...]
>
>> This is really useful, but not what I am looking for. I am effectively
>> looking for what this does, only for a whole thread. Something along the
>> lines of having a summary buffer showing only one thread (in notmuch see
>> screenshot [1]), and when I select a single article, it expands the
>> article *in the summary buffer* [2].
>
> Ah, I see. You want a combined summary + article view. Similar to what
> you get in gmail, I guess.
True - exactly like that.
> I don't think you'll find anything like this
> in gnus unfortunately as the various views are completely separate
> buffers. You want an inline expansion of the article within the summary
> buffer.
That's a pity, but I can live with that.
>
> Personally, I prefer the gnus approach in that I can see the thread
> structure in the summary window and then each individual article when
> desired. But obviously this is a personal taste issue!
I actually don't remember why I was looking for it. But it is most
definitely not a deal breaker to leave gnus.
If I need it, I can always search the message in notmuch.
Thanks a lot,
Rainer
--
Rainer M. Krug
email: RMKrug<at>gmail<dot>com
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-06-03 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877gig27tf.fsf@krugs.de>
2013-06-03 12:25 ` Eric S Fraga
2013-06-03 12:45 ` Rainer M Krug
2013-06-03 13:25 ` Eric S Fraga
2013-06-03 14:04 ` Rainer M Krug [this message]
2013-06-03 17:04 ` Adam Sjøgren
2013-06-04 7:50 ` Eric S Fraga
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=87d2s3qoio.fsf@krugs.de \
--to=rainer@krugs.de \
--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).