From: Martin Rohde <martin.rohde@gmx.de>
Subject: Re: 'g' in the group buffer still very slow
Date: Mon, 09 Dec 2002 23:38:35 +0100 [thread overview]
Message-ID: <87el8qlswk.fsf@gmx.de> (raw)
In-Reply-To: <84of7vxg2t.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Mon, 09 Dec 2002 18:22:34 +0100")
On Day 51 of The Aftermath 3168, Kai Großjohann wrote:
> You could create a new server definition that uses telnet instead of
> connecting directly. See the variable nntp-open-connection-function
> and the function nntp-open-telnet-stream, referenced from the
> variable. Maybe you can twiddle the telnet args such that echoing is
> used? You might wish to manually send stuff to the server in the
> server buffer (" *server foo *nntpd*" or somesuch, mind the leading
> space) using process-send-string. Then you can see whether the
> server echoes commands. (I hope that the echo removal isn't done in
> a process filter.)
Ok, now i used nntp-open-telnet-stream and looked at the server
buffer (thanks for the hints). There were several lines like "LIST
ACTIVE <newsgroup>", so commands are echoed and the lines are not
deleted. With nntp-open-network-stream or with an older version of
nntp.el the buffer is "clean".
Obviously my patch didn't worked, but now I figured out, that it
acted in the wrong buffer. And I found another problem:
After the test-command is send, I somehow have to find out, when the
response has arrived, so that I can look at the echo then. I thought
a (nntp-wait-for "^2.*\n" process buffer [...]) would work, but then
the echo is not found for unknown reasons (I have to confess, that I
don't really know, what I am doing here, maybe nntp-wait-for is
erasing the buffer for some reason...).
I just tried it with a (sleep-for 2) right after the
nntp-send-string-command to wait until the echo is in the server
buffer, just to see if the rest of my code is ok, and it "works"
now. (That means, nntp-delete-echo is set properly)
Of course, this is too ugly, so I need a reasonable possibility to
wait for the response. I thought of a kind of loop, but this
wouldn't be that much prettier IMHO. Is there a function i can use
for this?
> But "mode reader" is not a no-op, could that be a problem?
I'm not quite sure. I wanted to send a command, that doesn't have
affects on gnus and I read, that "mode reader" often is used as a
no-op. Maybe "slave" would be a better idea? (I don't have a clue
about nntp :)
Thanks for your advise,
Martin.
next prev parent reply other threads:[~2002-12-09 22:38 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
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 [this message]
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=87el8qlswk.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).