Gnus development mailing list
 help / color / mirror / Atom feed
From: Colin Rafferty <craffert@ml.com>
Subject: Re: opening speed for nnml groups
Date: 10 Sep 1997 11:07:46 -0400	[thread overview]
Message-ID: <ocr67s9gqbh.fsf@ml.com> (raw)
In-Reply-To: Lars Balker Rasmussen's message of "10 Sep 1997 10:43:15 +0200"

Lars Balker Rasmussen writes:

> When I edit a message[1], and I review the message (after having viewed
> some other message), the contents of the generated Article buffer
> appears to be the backlog[3].

> Playing around with this, it appears it's not just a backlog bug.  With
> gnus-keep-backlog at 0, after editing one message, I press up and space
> to view the former message and back down again to view the edited
> message, the Article buffer will still show the former message!

Actually, that still sounds like a backlog bug.  Setting it to 0 should
still be activating the keep-backlog code.

I would suggest setting it to nil (not zero), and see if you have the
same problems.

-- 
Colin


  reply	other threads:[~1997-09-10 15:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-02 12:01 Steinar Bang
1997-09-03 13:05 ` Steve Folkes
1997-09-03 15:01   ` Lars Balker Rasmussen
1997-09-03 19:45     ` Mark Eichin
1997-09-03 21:26     ` Russ Allbery
1997-09-04 14:55     ` Sean Doran
1997-09-04 15:39       ` Lars Balker Rasmussen
1997-09-04 21:44         ` Colin Rafferty
1997-09-05 12:20           ` David S. Goldberg
1997-09-05 15:21             ` Edit MIME messages (was: Re: opening speed for nnml groups) Kai Grossjohann
1997-09-05 15:57               ` David S. Goldberg
1997-09-09  7:06                 ` Steinar Bang
1997-09-10  8:43             ` opening speed for nnml groups Lars Balker Rasmussen
1997-09-10 15:07               ` Colin Rafferty [this message]
1997-09-13 23:54               ` Lars Magne Ingebrigtsen
1997-09-03 20:33 ` Ken Raeburn

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=ocr67s9gqbh.fsf@ml.com \
    --to=craffert@ml.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).