From: Max Froumentin <masmef@maths.bath.ac.uk>
Subject: Re: reading news over telnet
Date: 19 Aug 1999 16:07:48 +0100 [thread overview]
Message-ID: <ptvr9kzolkr.fsf@scratchy.maths.bath.ac.uk> (raw)
In-Reply-To: dsg@mitre.org's message of "17 Aug 1999 16:37:38 -0400"
...is possible, even though I've had to modify the gnus source (commented
out 1 line):
AFAIK Whatever controls the traffic between the subnet here and the
outside world filters out NNTP as well as RLOGIN connections, but not
TELNET. This is why using
(setq nntp-open-connection-function nntp-open-rlogin) doesn't seem to work.
nntp-open-telnet didn't work either but for a different reason: just
after reading the user password, nntp-open-telnet erases the terminal
buffer and then waits for a prompt:
(process-send-string
proc (concat
(or nntp-telnet-passwd
(setq nntp-telnet-passwd
(mail-source-read-passwd "Password: ")))
"\n"))
(erase-buffer)
(nntp-wait-for-string nntp-telnet-shell-prompt)
What happens in my case is that the prompt is always written in the
buffer *before* the latter is erased. Thus nntp-wait-for-string
hangs. Everything seems to work when I comment out (erase-buffer).
My group parameters are now:
(nntp "firewall"
(nntp-address "mary.bath.ac.uk")
(nntp-open-connection-function nntp-open-telnet)
(nntp-end-of-line "\n")
(nntp-telnet-parameters
("exec" "telnet" "-8" "${NNTPSERVER:=news.freshmeat.net}" "nntp")))
I suppose I could send a patch or something to have this corrected in
the next gnus release, but with my limited knowledge of
gnus/emacs/elisp I'd rather be cautious and avoid damaging the nntp
backend...
Maybe someone who knows more than me will verify this change and
approve it.
Max.
next prev parent reply other threads:[~1999-08-19 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-17 14:33 Max Froumentin
1999-08-17 14:42 ` Max Froumentin
1999-08-17 15:04 ` Kai Großjohann
1999-08-17 18:14 ` Max Froumentin
1999-08-17 19:11 ` David S. Goldberg
1999-08-17 19:22 ` Toby Speight
1999-08-17 20:37 ` David S. Goldberg
1999-08-19 15:07 ` Max Froumentin [this message]
1999-09-24 18:27 ` Lars Magne Ingebrigtsen
1999-08-17 15:57 ` Sam Falkner
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=ptvr9kzolkr.fsf@scratchy.maths.bath.ac.uk \
--to=masmef@maths.bath.ac.uk \
/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).