From: Marcus Frings <iam-est-hora-surgere@despammed.com>
Subject: Re: [Q]: gnus-summary-refer-parent-article, what does it deserve ?
Date: Wed, 03 Mar 2004 22:48:58 +0100 [thread overview]
Message-ID: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87oerda9f9.fsf@gothgoose.net> (raw)
In-Reply-To: <plop873c8q9wtm.fsf@gnu-rox.org>
* Xavier Maillard <zedek@gnu-rox.org> wrote:
> Today I incidentally discovered a gnus feature.
> When in a summary buffer, hit '^' and you can (provided it is possible)
> read the ancestor(s) of an article.
Yes, it's a very nice feature, isn't it? :-)
> I admit it could be useful but my problem is I don't even know when
> people use it exactly (if ever used).
> So can somebody explain me when does he use this feature ?
I use it quite often. In addition I have:
;; How to find the parent article
(setq gnus-refer-article-method
'(current
(nntp "iridium.home.local") ; first my local inn, then
(nntp "news.t-online.de") ; news.t-online.de, then
(nnweb "google" (nnweb-type google)) ; groups.google.com and finally
(nntp "news.gmane.org"))) ; news.gmane.org
Since I let Gnus show me new articles only and I often need to go up
within the thread I usually hit ^ instead of rebuilding the thread by `A
R' or `A T'. Besides my local inn stores articles just for 4 months so
it is a great feature to look at other newsservers with the code
mentioned above.
Regards,
Marcus
--
"This elevator serves me alone. I have complete control over
this entire level. With cameras as my eyes and nodes as my
hands, I rule here, insect."
(Shodan in System Shock)
next prev parent reply other threads:[~2004-03-03 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 8:08 Xavier Maillard
2004-03-03 21:35 ` : " Adam Sjøgren
2004-03-05 8:37 ` Kai Grossjohann
2004-03-03 21:48 ` Marcus Frings [this message]
2004-03-03 22:42 ` [Q]: " Xavier Maillard
2004-03-04 18:37 ` Marcus Frings
2004-03-06 13:06 ` Xavier Maillard
2004-03-06 14:13 ` Marcus Frings
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=vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87oerda9f9.fsf@gothgoose.net \
--to=iam-est-hora-surgere@despammed.com \
--cc=protagonist@gmx.net \
/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).