MIME-Version: 1.0
In-Reply-To: <49E3BA94.8090400@cornell.edu>
References: <007d01c9bc7b$afae8820$0f0b9860$@com> 	 <49E3BA94.8090400@cornell.edu>
Date: Mon, 13 Apr 2009 18:58:02 -0400
Message-ID: <17393e3e0904131558s16c1e9eexb1590f89d5ebe72d@mail.gmail.com>
Subject: Re: Emacs key bindings not working
From: Matt Wozniski <godlygeek@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Mon, Apr 13, 2009 at 6:20 PM, Ken Brown wrote:
> On 4/13/2009 5:06 PM, Brandon Olivares wrote:
>>
>> I'm noticing not all built-in key bindings are working. I'm trying to set
>> a
>> mark, and read that you use C-@ or C-SPC, but neither are working. C-@
>> does
>> nothing, and C-SPC inserts a space.
>>
>> It tells me C-M-\ should indent the region, but it doesn't do so.
>
> This is a terminal issue. =C2=A0The key bindings work fine if you run ema=
cs under
> X (which is the way I almost always use it) or under mintty. =C2=A0They p=
robably
> work under rxvt also, but I haven't tried that. =C2=A0You may have to rem=
ove tty
> from your CYGWIN variable if you use these other terminals. =C2=A0(I'm not
> positive about that.)

No, mintty, rxvt, and xterm all already behave as though CYGWIN=3Dtty
was set, and there's no way to stop them from doing that.  Setting
CYGWIN=3Dtty just makes cmd.exe, command.com, powershell, etc can be
made to use the cygwin tty layer as well.

See http://www.cygwin.com/cygwin-ug-net/using-cygwinenv.html

(no)tty - if set, Cygwin enables extra support (i.e., termios) for
UNIX-like ttys in the Windows console. It is not compatible with some
Windows programs. Defaults to not set, in which case the tty is opened
in text mode.

The salient point is that it only affects "the Windows console".

~Matt

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