From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Strange auto-caching
Date: Wed, 12 Feb 2003 10:20:35 -0600 [thread overview]
Message-ID: <uwuk5eai4.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <84r8adq0c4.fsf@lucy.is.informatik.uni-duisburg.de>
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> It's FIXED!!! As it turns out, gnus-summary-update-mark updates the
>> current line rather than the current article. :( Why do programs
>> insist on working the way they were programmed rather than how we
>> expect them to work?
>
> I've now run "cvs update" and I'm running the new version now.
> But I still see the old problem.
>
> However, I haven't tried on new articles -- the article in question
> is an old article, from the time when Gnus still didn't have your
> newest change. Not sure if this is relevant.
>
> I'm surprised that you are looking in this area. Usually, the
> current article and the current line are the same, when I use Gnus.
> It definitely happens on too many articles for the
> current-art/current-line mismatch to be the cause.
>
What I found occurred when several articles were marked as
downloadable. In this case, the current line points to the the last
marked article.
There may also have been a problem in that a couple of the summary
update functions move point to the next line. So if I write (progn (update)
(update) (update)) I end up making changes to three articles rather than
one. Still checking on this one.
Kevin
next prev parent reply other threads:[~2003-02-12 16:20 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
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 [this message]
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=uwuk5eai4.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).