From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Threading wrong if showing undownloaded articles
Date: Sun, 09 Mar 2003 00:20:51 -0600 [thread overview]
Message-ID: <u4r6dhxh8.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <84llzp3hqq.fsf@lucy.is.informatik.uni-duisburg.de>
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> Right, the function that I provided should be able to refresh the
>> undownloaded articles. I suspect that the data structures used by the
>> summary are being corrupted. I'd like you to find out if that is
>> true.
>
> I have now tested your function test1 on an article and it doesn't
> appear to do anything (except to advance point to the next line).
>
> I'm not 100% sure if the originally reported behavior was the same as
> what I'm seeing now. What I'm seeing now is that all articles are
> shown correctly initially (the threading is correct). But when I
> select a non-downloaded article, the summary line changes. In
> particular, the %B part changes. It appears that the new %B macro
> always expands to gnus-sum-thread-tree-single-leaf, preceded by one
> or two levels of indentation. (It's always the same number of
> levels, but I don't know the number offhand.)
>
> Hm. The thing that's inserted there is
> gnus-tmp-thread-tree-header-string, according to
> gnus-summary-line-format-alist. So a hypothesis is that this
> variable is b0rked.
>
> Which function is called to show the summary line when I select an
> article?
>
> Ah. gnus-tmp-thread-tree-header-string is only set in one spot, in
> gnus-summary-prepare-threads. Hmm... Oh! Selecting an article
> appears to call gnus-summary-update-article-line which calls
> gnus-summary-insert-line which does not know about the correct value.
>
> Is this analysis correct?
It sure looks it. Let's try making a small change to
gnus-agent-fetch-selected-article :).
Replace the entire call to gnus-summary-update-article-line with
(gnus-summary-update-line gnus-current-article)
Kevin
next prev parent reply other threads:[~2003-03-09 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 14:51 Kai Großjohann
2003-02-28 5:46 ` Kevin Greiner
2003-02-28 13:07 ` Kai Großjohann
2003-02-28 13:52 ` Kevin Greiner
2003-03-08 17:12 ` Kai Großjohann
2003-03-08 17:31 ` Kai Großjohann
2003-03-09 6:20 ` Kevin Greiner [this message]
2003-03-09 11:19 ` Kai Großjohann
2003-03-09 14:33 ` Kevin Greiner
2003-03-09 16:39 ` Kai Großjohann
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=u4r6dhxh8.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.com \
/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).