From: matthias@my.gnus.org (Matthias Wiehl)
Subject: Re: Can't mark negative article numbers
Date: Sat, 03 Nov 2001 01:14:02 -0500 [thread overview]
Message-ID: <83y9loqt3p.fsf@mail.socha.net> (raw)
In-Reply-To: <deathsquad.87y9lopx7b.fsf@socha.net> ("Robin S. Socha"'s message of "Fri, 02 Nov 2001 18:30:48 -0500")
"Robin S. Socha" <robin-dated-1005003013.83ef58@socha.net> writes:
> Okay, so I say ^ in the summary buffer and then !. No workie. Why?
,----[ <vxkae8uu35z.fsf@cinnamon.vanillaknot.com> ]
| Karl Kleinpaste <karl@charcoal.com> writes:
|
| Yes. This is a fairly fundamental issue. You see, when you chase to
| a parent article, it may or may not have come from within the same
| group as the group you're currently reading. If you're reading
| gnu.emacs.gnus and chase to an article's parent, you may be reading an
| article posted (only) to news.software.readers. What if you don't
| read n.s.r? What does it mean to mark an article to which you don't
| even have access in the normal case?
|
| Generally, if Gnus can figure out where in the current group a
| chased-to article belongs, it will not number it negatively, but will
| show it with its normal within-the-group numbering. It is only
| articles from outside the current group that get such treatment.
`----
,----[ <vafk7xizui7.fsf@lucy.cs.uni-dortmund.de> ]
| Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
|
| When you hit `^', Gnus looks to see if it has downloaded the header
| for this message already. If so, it uses the article number found
| there. But if not, then Gnus fetches the right article by message-id,
| but it does not look to find the right article number for this
| message-id. Note that the article might come from a different group,
| so it's not possible to always assign a good number.
`----
next prev parent reply other threads:[~2001-11-03 6:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 23:30 Robin S. Socha
2001-11-02 23:41 ` ShengHuo ZHU
2001-11-02 23:56 ` Robin S. Socha
2001-11-03 0:19 ` ShengHuo ZHU
2001-11-03 16:37 ` Kai Großjohann
2001-11-03 6:14 ` Matthias Wiehl [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-19 18:51 Thomas Skogestad
2001-04-19 19:20 ` Karl Kleinpaste
2001-04-19 19:23 ` Paul Jarc
2001-04-21 16:34 ` Anssi Saari
2001-04-21 22:42 ` Paul Jarc
2001-04-22 6:06 ` Stainless Steel Rat
2001-04-22 8:40 ` Kai Großjohann
2001-04-22 15:04 ` Stainless Steel Rat
2001-05-04 21:51 ` Florian Weimer
2001-05-06 7:04 ` Yair Friedman (Jerusalem)
2001-05-06 7:57 ` Russ Allbery
2001-05-06 8:02 ` Florian Weimer
2001-04-22 17:57 ` Paul Jarc
2001-01-13 19:05 Karl Eichwalder
2001-01-13 19:33 ` Kai Großjohann
2001-01-14 6:31 ` Karl Eichwalder
2001-04-22 12:44 ` Karl Eichwalder
2001-01-14 5:13 ` Karl Kleinpaste
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=83y9loqt3p.fsf@mail.socha.net \
--to=matthias@my.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).