X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_05,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4DAF140A.8050501@cs.umass.edu> Date: Wed, 20 Apr 2011 13:12:42 -0400 From: Eliot Moss Reply-To: moss@cs.umass.edu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Why doesn't ~/inputrc work References: <87ei4w6hvx.fsf@newsguy.com> <4DAF035B.6030408@redhat.com> In-Reply-To: <4DAF035B.6030408@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 4/20/2011 12:01 PM, Eric Blake wrote: > On 04/20/2011 09:51 AM, Harry Putnam wrote: > Do you have CRLF line endings on your ~/.inputrc? That would explain > failures. To fix it, run 'd2u ~/.inputrc'. Other than that, it works > for me, so I'm not sure why you're having problems. A great suggestion. I also thought of two other things: - If the INPUTRC environment variable is set, you may be reading something different from what you think - How and whether a terminal generates meta- keys will clearly affect the specific bindings you mentioned. So you may need to dig into the specific terminal and into stty settings for the terminal driver Best -- Eliot Moss -- 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