Gnus development mailing list
 help / color / mirror / Atom feed
From: Bill White <billw@wolfram.com>
Subject: flashing raw buffers
Date: 10 Dec 1999 20:33:56 -0600	[thread overview]
Message-ID: <ruozovixl2j.fsf@g.wolfram.com> (raw)

Sorry, this isn't a pr0n posting as you might think from the subject.

Gnus v5.8.3 from cvs as of 2315 GMT Fri 10 Dec

GNU Emacs 20.4.1 (i586-pc-linux-gnu, X toolkit) of Fri Jul 16 1999 on
g.wolfram.com

When gnus generates summary and article buffers, I see a lot of raw
unprocessed buffers flash by before the final buffers are
presented. Is anyone else seeing this? What might be causing it? It's
new (to me) in the more recent gnusae, perhaps the last week or a bit
more.

I update and compile with this:

cd ~/emacs-lisp/gnus
cvs update
./configure && make

Thanks -

bw
-- 
Bill White . billw@wolfram.com . http://members.wri.com/billw
Having children is like having a bowling alley installed in 
your brain. --Martin Mull


             reply	other threads:[~1999-12-11  2:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-11  2:33 Bill White [this message]
2000-04-21 18:47 ` Lars Magne Ingebrigtsen
2000-04-21 19:13   ` Lars Magne Ingebrigtsen

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=ruozovixl2j.fsf@g.wolfram.com \
    --to=billw@wolfram.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).