Gnus development mailing list
 help / color / mirror / Atom feed
From: Ketil Z Malde <ketil@ii.uib.no>
Cc: ding@ifi.uio.no
Subject: Re: Getting articles asynchronously.....
Date: Tue, 16 Jan 1996 11:34:02 +0100	[thread overview]
Message-ID: <9601161034.AA07122@krone.ii.uib.no> (raw)
In-Reply-To: Steven L Baur's message of 15 Jan 1996 12:36:44 -0800


>>>>> "Greg" == Greg Stark <gsstark@MIT.EDU> writes:

    Greg> There's a lot of real gains to be made here.  Gnus would be
    Greg> a lot more useful if it didn't lock up Emacs while doing
    Greg> long operations like listing groups, checking for bogus
    Greg> groups, or entering a group (once took me over 30 minutes).

>>>>> "Steven" == Steven L Baur <steve@miranova.com> writes:

  Steven> It's making less and less sense to me to have Gnus wait
  Steven> while reading the NNTP active file at startup, with mail
  Steven> to be read and such.

Not to mention a couple of nnkiboze processes that would be sooo nice
to run in the background.  I assume a multithreaded emacs is
non-trivial? 

-kzm


  reply	other threads:[~1996-01-16 10:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-12-26  9:16 Patrick Audley
1995-12-26 14:18 ` Stainless Steel Rat
1995-12-26 20:57   ` Patrick Audley
1995-12-26 23:34     ` Stainless Steel Rat
1995-12-27  1:18   ` Felix Lee
1996-01-03  9:20     ` Lars Magne Ingebrigtsen
1995-12-28  4:53   ` Mark W. Eichin
1995-12-28 13:35     ` Greg Stark
1996-01-15  9:15       ` Greg Stark
1996-01-15 20:36         ` Steven L Baur
1996-01-16 10:34           ` Ketil Z Malde [this message]
1996-01-16 11:05             ` Greg Stark
1996-01-16 13:05               ` Massimo Campostrini
     [not found]               ` <zqbn99ny@totally-fudged-out-message-id>
1996-01-17  2:51                 ` Lars Magne Ingebrigtsen
1996-01-17  2:51           ` 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=9601161034.AA07122@krone.ii.uib.no \
    --to=ketil@ii.uib.no \
    --cc=ding@ifi.uio.no \
    /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).