Gnus development mailing list
 help / color / mirror / Atom feed
From: list.ding@rwhitby.net
Subject: Re: nntp telnet connection with remote command echoes
Date: 10 Jul 2000 14:52:00 +0930	[thread overview]
Message-ID: <m3og468sqv.fsf@a11375-rw.asc.corp.mot.com> (raw)
In-Reply-To: Rod Whitby's message of "06 Jul 2000 09:02:19 +0930"

Rod Whitby <list.ding@rwhitby.net> writes:
> I'd like to make some changes to nntp.el to handle remote telnet
> programs that echo commands.  I'm looking for advice on whether there
> is another way to solve the problem instead of changing nntp.el

Can I assume from the total lack of responses that I should just go
ahead and post the diff ? :-)

Is there no-one else on the list who has to deal with a telnet that
echoes commands ?

-- 
-- Rod Whitby, Snr Staff Engr, Electronic Design Automation --
-- Motorola Australia Software Centre - Adelaide, Australia --
-- Phone: +61 8 8203 3526, Fax: +61 8 8203 3501, <GMT+9:30> --




  reply	other threads:[~2000-07-10  5:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-05 23:32 Rod Whitby
2000-07-10  5:22 ` list.ding [this message]
2000-07-10 11:49   ` Kai Großjohann
2000-07-11  0:22     ` Rod Whitby
2000-08-14 19:05 ` 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=m3og468sqv.fsf@a11375-rw.asc.corp.mot.com \
    --to=list.ding@rwhitby.net \
    /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).