Gnus development mailing list
 help / color / mirror / Atom feed
From: Xavier Maillard <zedek@gnu-rox.org>
Subject: [Q]: gnus-summary-refer-parent-article, what does it deserve ?
Date: Wed, 03 Mar 2004 09:08:53 +0100	[thread overview]
Message-ID: <plop873c8q9wtm.fsf@gnu-rox.org> (raw)

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

Hi,

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.

I admit it could be useful but my problem is I don't even know when
people use it exactly (if ever used).

The docstring says:

,----
| ^ runs the command gnus-summary-refer-parent-article
|    which is an interactive compiled Lisp function in `gnus-sum'.
| It is bound to ^, A r, A ^, <menu-bar> <article> <fetch parent of article>.
| (gnus-summary-refer-parent-article N)
| 
| Refer parent article N times.
| If N is negative, go to ancestor -N instead.
| The difference between N and the number of articles fetched is returned.
`----

I thought I could use this when threads where broken but most of the
time, when a thread is broken by a post, it is highly likely it doesn't
have a references header and so '^' is not that useful (not to say
useless)in that case.

So can somebody explain me when does he use this feature ?

Thank you,

zeDek
-- 
GnusFR  (http://www.gnusfr.org)
EmacsFR (http://www.emacsfr.org)

.emacs: Because customisation is fun!


[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

             reply	other threads:[~2004-03-03  8:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03  8:08 Xavier Maillard [this message]
2004-03-03 21:35 ` : " Adam Sjøgren
2004-03-05  8:37   ` Kai Grossjohann
2004-03-03 21:48 ` [Q]: " Marcus Frings
2004-03-03 22:42   ` 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=plop873c8q9wtm.fsf@gnu-rox.org \
    --to=zedek@gnu-rox.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).