To: cygwin@cygwin.com
From: Harry Putnam <reader@newsguy.com>
Subject: Re: Why doesn't ~/inputrc work
Date: Wed, 27 Apr 2011 23:49:10 -0500
Lines: 20
Message-ID: <874o5jc75l.fsf@newsguy.com>
References: <87ei4w6hvx.fsf@newsguy.com> <4DAF035B.6030408@redhat.com>	<4DAF140A.8050501@cs.umass.edu> <87aafbc86s.fsf@newsguy.com>
Mime-Version: 1.0
Content-Type: text/plain
User-Agent: Gnus/5.110016 (No Gnus v0.16) Emacs/24.0.50 (gnu/linux)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Harry Putnam <reader@newsguy.com> writes:

> I guess a way to test would be to use a different entry that relies on
> something besides the meta (alt) key... I've never used anything else
> since my inputrc files are not that complex.
>
> Can you show an example of an entry that uses some other combo?  And
> explain how one would enter it into an .inputrc When I see those
> Sequences and ctrl char... I get very confused... and not sure how to
> create an inputrc entry using them.

I found some really simple examples in man readline.

Something like `Control-o: "some-string"'

Works as expected and inserts `some-string' into the cmdline when I
press ` Ctrl-o', so apparently it IS some problem with the meta
(alt) key.

Any IDEAS as to what to do about it would be welcome.


--
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