Gnus development mailing list
 help / color / mirror / Atom feed
From: Martin Rohde <martin.rohde@gmx.de>
Subject: Re: 'g' in the group buffer still very slow
Date: Mon, 09 Dec 2002 00:33:49 +0100	[thread overview]
Message-ID: <87wumk5bmq.fsf@gmx.de> (raw)
In-Reply-To: <84adjg8fbd.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Sun, 08 Dec 2002 20:45:58 +0100")

On Day 50 of The Aftermath 3168, Kai Großjohann wrote:

> krause@my.gnus.org (Sebastian D.B. Krause) writes:
>
>> Okay, as we don't need this code when Gnus has a direct NNTP
>> connection to the server (when nntp-open-connection-function is set
>> to nntp-open-network-stream), I suggest -- as a workaround -- to
>> enable this code only when nntp-open-connection-function is *not*
>> nntp-open-network-stream. I've tested my small patch (see below) and
>> it makes fetching the active file much faster without the problems I
>> had with telnet and local echo when I removed the code with the old
>> patch quoted below.
>
> There is a bug.  You write (unless nntp-open-connection-function
> 'nntp-open-network-stream statements...).  The condition here is the
> variable nntp-open-connection-function, it is tested whether the
> variable is nil.  The quoted symbol is an expression which is
> evaluated by has no effect.
>
> I've committed something similar to your patch.

Like Sebastian mentioned before,

,----
| 
|  (unless (and wait-for
| 	     (equal nntp-open-connection-function
| 		    'nntp-open-network-stream))
`----

doesn't work. It has to be "or" instead of "and"...

> I think what should be done is to look, after the connection has been
> established, whether the commands are echoed.  If so, set a
> variable.  Then change the condition to look at that variable.

If I get it right, you can almost take the code for that from
nntp-send-command* and put it into nntp-open-connection. I will send
a patch, if it works.


Martin



  parent reply	other threads:[~2002-12-08 23:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-21 20:16 Sebastian D.B. Krause
2002-07-26 12:45 ` Simon Josefsson
2002-07-26 12:52   ` Kai Großjohann
2002-12-08 18:00   ` Sebastian D.B. Krause
2002-12-08 19:45     ` Kai Großjohann
2002-12-08 20:28       ` Sebastian D.B. Krause
2002-12-08 23:33       ` Martin Rohde [this message]
2002-12-09  7:49         ` Kai Großjohann
2002-12-09 14:02           ` Martin Rohde
2002-12-09 17:22             ` Kai Großjohann
2002-12-09 22:38               ` Martin Rohde
2002-12-10 18:30                 ` Martin Rohde
2002-12-11  4:13                   ` kgreiner
2002-12-11 20:05                     ` Martin Rohde
2002-12-11 21:09                       ` kgreiner
2002-12-12 11:37                       ` Kai Großjohann
2002-12-13 15:41                         ` Martin Rohde
2002-12-13 16:24                           ` Kai Großjohann
2002-12-13 17:18                             ` Martin Rohde
2002-12-14 12:52                               ` Kai Großjohann
2002-12-14 14:11                                 ` Martin Rohde
2002-12-11  8:21                   ` Kai Großjohann
2002-12-09  8:36         ` Kai Großjohann

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=87wumk5bmq.fsf@gmx.de \
    --to=martin.rohde@gmx.de \
    /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).