Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Strange auto-caching
Date: Tue, 11 Feb 2003 17:34:55 +0100	[thread overview]
Message-ID: <84adh2ojww.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <ur8af70sk.fsf@xpediantsolutions.com>

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

> From what you are describing gnus-agent-fetch-selected-article updates
> the internals correctly.  The problem has to be in its call to
> gnus-summary-update-article-line.  I've already found, and I thought,
> fixed a problem in this call.  There must be something else going
> wrong.  Can you step through it to see what is happening?  What
> happened before was that g-s-u-a-l jumped to, and updated, the wrong
> line in the summary.

My problem has nothing to do with gnus-summary-update-article-line.  I
think...  I just did M-x edebug-defun RET on it, then entered a group
and got this result (slightly massaged because of UTF-8 characters in
thread trees):

-   Thu 16.01., 19k: Robert J. Chass | Re: errors in Tramp FTP, yet file fetched
-  +Sat 18.01.,3.7k: Kai Großjohann  | Todo: Forbidden word "path"
-   Sun 19.01.,2.5k: Michael Albinus |  \-
+Q  Jan 01 '70,0.0k:                 | Re: Preserve permissions after backup?
-   Mon 27.01.,2.3k: Eli Zaretskii   | \-
-   Mon 27.01.,2.0k: Richard Stallma |  \-
+   Tue 28.01.,2.3k: Michael Albinus | Re: tramp (2.0.28); ange-ftp stopped working
+   Tue 28.01.,3.0k: Michael Albinus | Re: Todo

%O is the first char in each line.

The function gnus-summary-update-article-line was not called.

I verified that the `-' marked articles were also fetched by exiting
the group, going unplugged, reentering the group, selecting Eli's or
Richard's article.

Something else is also wrong in that `.' does not jump to `-' marked
articles, only to `+' marked ones.  Maybe
gnus-summary-first-unread-article and %O are accessing the same,
wrong, data structure?

Is there another function that I could trace through?

Is anyone else seeing similar problems?
-- 
A turnip curses Elvis



  reply	other threads:[~2003-02-11 16:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-09 15:22 Kai Großjohann
2003-02-11  7:07 ` Kevin Greiner
2003-02-11 16:34   ` Kai Großjohann [this message]
2003-02-11 17:49     ` Kevin Greiner
2003-02-11 19:19       ` Kai Großjohann
2003-02-11 18:19     ` Kevin Greiner
2003-02-11 19:19       ` Kai Großjohann
2003-02-11 19:30         ` Kevin Greiner
2003-02-11 19:52           ` Kai Großjohann
2003-02-11 20:54             ` Kevin Greiner
2003-02-12 10:07               ` Kai Großjohann
2003-02-12 16:20                 ` Kevin Greiner
2003-02-12 16:58                   ` Kai Großjohann
2003-02-13  0:36                     ` Kevin Greiner
2003-02-13  2:19                     ` Kevin Greiner
2003-02-13 11:16                       ` Kai Großjohann
2003-02-13 11:22                       ` Kai Großjohann
2003-02-11 19:30     ` Kai Großjohann
2003-02-11 19:44       ` Kevin Greiner
2003-02-11 19:48     ` Kai Großjohann
2003-02-11 20:31       ` Danny Siu

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=84adh2ojww.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@uni-duisburg.de \
    /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).