Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 20 May 2002 20:04:38 +0300 (EEST) From: rudy AT viper DOT iasi DOT rdsnet DOT ro To: cygwin AT cygwin DOT com Subject: Re: Key mappings in ssh Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > Is this ssh-ing out of your cygwin box or into it? I am using a third party client to connect to sshd on cygwin. Thanks for the tip with stty. It worked ok. Now I'm facing the following problem: -I need to have stty erase ^? while connecting with ssh to cygwin -and on the other hand I need stty erase ^H in bash prompts So I try writing a script (which can't rely on /var/run/utmp, as cygwin doesn't seem to maintain it) to tell which stty param to run... ps reports processes using either con either 0 1 2 ... tty's, so I should be able to detect this. I still don't know how but... :-) Another question: linux man page for termcap tells that kb is a string parameter. Indeed, on linux systems (and not only) in /etc/termcap we can find, for example ...:kb=\177:... Why does the cygwin termcap only specifies ...:kb:... ? Thanks again, rudy PS btw: I ran stty -a both on bash prompt and ssh prompt. Why do they report differently? Does the ssh protocol negociates this kind of settings on startup? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/