Gnus development mailing list
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: Benchmarking Gnus
Date: Wed, 16 Jan 2002 11:51:37 -0500	[thread overview]
Message-ID: <87n0zejl2e.fsf@paradoxical.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0201161337460.27002-100000@slipsten.extundo.com>

Simon Josefsson <jas@extundo.com> writes:

> A long term solution would be to redesign this stuff and make it run
> asynchronously.  The summary buffer would appear immediately
> containing as many empty lines as there are messages that should be
> shown, and then things are populated in the background.  This might
> even give us some more flexibility, like allowing backends to
> perform threading (IMAP supports this).

Er, doesn't this require some support from emacs for threads?  Isn't
there none?

> But long term solutions should perhaps be targetted at Guile..  gimme a 
> guile emacs! :-)

Hehe, yeah, but that's a while away, I think :)

-- 
Josh Huber



  reply	other threads:[~2002-01-16 16:51 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-16  2:12 Lars Magne Ingebrigtsen
2002-01-16  4:42 ` Russ Allbery
2002-01-19 23:25   ` Lars Magne Ingebrigtsen
2002-01-16  6:35 ` Jesper Harder
2002-01-19 23:25   ` Lars Magne Ingebrigtsen
2002-01-16 12:45 ` Simon Josefsson
2002-01-16 16:51   ` Josh Huber [this message]
2002-01-16 17:21     ` Karl Kleinpaste
2002-01-16 19:26   ` Steinar Bang
2002-01-17  2:06   ` Daniel Pittman
2002-01-17 17:04 ` Ami Fischman
2002-01-19 23:28   ` Lars Magne Ingebrigtsen
2002-01-20 19:11     ` Ami Fischman
2002-01-20 19:15       ` Lars Magne Ingebrigtsen
2002-01-20 20:05         ` Ami Fischman
2002-01-20 20:03           ` Lars Magne Ingebrigtsen
2002-01-20 20:33             ` Ami Fischman
2002-01-18 23:42 ` Jesper Harder
2002-01-19 11:38   ` Simon Josefsson
2002-01-27  0:30 Lars Magne Ingebrigtsen
2002-01-27  0:35 ` IPmonger
2002-01-27  0:45   ` Lars Magne Ingebrigtsen
2002-01-29 16:03     ` IPmonger
2002-01-30  8:53       ` Kai Großjohann
2002-01-30 16:42         ` IPmonger
2002-01-30 17:38           ` Kai Großjohann
2002-01-30 18:15             ` Lars Magne Ingebrigtsen
2002-01-30 18:42               ` Josh Huber
2002-02-04 23:35       ` IPmonger
2002-02-04 23:48         ` IPmonger
2002-02-04 23:57         ` Daniel Pittman
2002-01-30 22:02 ` Wes Hardaker
2002-01-30 22:09   ` IPmonger
2002-01-31  1:25     ` Wes Hardaker
2002-01-31  3:22       ` ShengHuo ZHU
2002-01-31 15:29         ` Wes Hardaker
2002-01-31 16:34       ` Steinar Bang
2002-01-31 16:54         ` Bjørn Mork
2002-01-31 20:50           ` Steinar Bang
2002-01-31 22:35             ` Bjørn Mork
2002-02-01  7:14               ` Steinar Bang
2002-02-01  9:17                 ` Bjørn Mork
2002-02-01 10:00                   ` Steinar Bang
2002-02-01 11:24                     ` Bjørn Mork
2002-02-01 11:29                     ` Simon Josefsson
2002-02-01 12:52                       ` Steinar Bang
2002-02-01 13:40                         ` Simon Josefsson
2002-02-01 14:12                           ` Steinar Bang
2002-02-01 14:39                             ` ShengHuo ZHU
2002-02-01 15:01                               ` Simon Josefsson
2002-02-01 15:31                                 ` Steinar Bang
2002-02-01 14:59                             ` Simon Josefsson
2002-02-01 15:18                               ` Steinar Bang
2002-02-01 16:51         ` Wes Hardaker

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=87n0zejl2e.fsf@paradoxical.net \
    --to=huber@alum.wpi.edu \
    /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).