public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <warren@etr-usa.com>
To: Andrey Repin <cygwin@cygwin.com>
Subject: Re: Telnet in latest Cygwin
Date: Thu, 08 Aug 2013 18:30:00 -0000	[thread overview]
Message-ID: <5203E3D9.2090509@etr-usa.com> (raw)
In-Reply-To: <1326593020.20130808150801@mtu-net.ru>

On 8/8/2013 05:08, Andrey Repin wrote:
>
> Though, I fail to see, how Cygwin telnet is different from, say PuTTY. Or
> native Windows telnet.

Windows 8 doesn't come with telnet.exe installed by default, and when 
you install it from Programs and Features, it's invisible to Cygwin 32, 
apparently due to the SxS madness.

Cygwin 64 *does* see it, but attempting to run it just drops you right 
back at a prompt, immediately.

Even if it did run, wouldn't things like Ctrl-] break due to the 
problems Cygwin currently has running interactive native console programs?

Windows' telnet.exe doesn't even run particularly well within cmd.exe. 
Telnetting to a local web server here, it didn't do local echo properly, 
so I couldn't see whether I'd typed "GET / HTTP1.0" correctly.  (I had 
Cygwin telnet.exe renamed to cygtelnet.exe during this time, to ensure I 
wasn't picking it up by accident.)

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2013-08-08 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07 21:19 Andy Davidson
2013-08-07 21:37 ` Larry Hall (Cygwin)
2013-08-08  7:09   ` Corinna Vinschen
2013-08-08 11:20     ` Andrey Repin
2013-08-08 18:30       ` Warren Young [this message]
2013-08-09 14:42         ` Paul Allen
2013-10-27 20:45     ` Ralph Siegler
2013-10-28 14:03       ` Robert Klemme
2014-01-25 12:15   ` zeev
2014-01-25 19:03     ` Christopher Faylor

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=5203E3D9.2090509@etr-usa.com \
    --to=warren@etr-usa.com \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).