delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/09/15/07:44:56

X-Spam-Check-By: sourceware.org
Message-ID: <450A923B.2050405@byu.net>
Date: Fri, 15 Sep 2006 05:44:59 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Thunderbird/1.5.0.5 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com, blevy AT qualcomm DOT com
Subject: Re: completion-ignore-case problem with cygwin
References: <C7A98C6EB85FFF4FAE03BD695D68EC7612182E AT NAEX05 DOT na DOT qualcomm DOT com>
In-Reply-To: <C7A98C6EB85FFF4FAE03BD695D68EC7612182E@NAEX05.na.qualcomm.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ugh - http://cygwin.com/acronyms/#TOFU reformatted.

> -----Original Message-----
> From: Igor Peshansky [mailto:pechtcha AT dont DOT do DOT that]
                               ^^^^^^^^^^^^^^^^^^^^^
Ugh - spam feeder.  http://cygwin.com/acronyms/#PCYMTNQREAIYR

>
> Yes, it definitely seems to be turned off.  Are you sure your ~/.inputrc
> gets read?  Is your HOME variable set correctly?
>
>
> Try running 'bash -vx --login -i' to see what commands are executed when
> you run a login shell.  Perhaps there is a startup script somewhere that
> executes the bind command to turn completion-ignore-case off.
>
> HTH,
> 	Igor


According to Levy, Bruce on 9/14/2006 4:40 PM:
> Hi Igor,
> 
> Thank you very much for your reply.
> 
> I invoked 'bash -vx --login -i' and watched the commands that were being
> executed.  I did NOT see any reference to completion-ignore-case.
> Should I see the lines in .inputrc being executed?  I did not see any
> .inputrc output.

The sourcing of ~/.inputrc will not show up in the bash trace.  If you are
desparate, you can use strace to see what files bash sources, but the
output is quite long and should not be posted here without an explicit
request.

> 
> From my bash shell I ran bind 'set completion-ignore-case on' and that
> worked perfectly.  I then tried putting that line into .bashrc and that
> also worked.  So, I have a workaround, but I'm not sure why .inputrc is
> not invoked.

Igor's question about HOME is important - are you changing $HOME inside of
your .bashrc?  It could be that bash IS attempting to source ~/.inputrc,
but at a time when ~ is incorrectly set.  You can also set the INPUTRC
environment variable (prior to bash's execution) to tell bash to look
somewhere else, to ensure that your file is picked up during readline
initialization.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
volunteer cygwin readline maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFCpI784KuGfSFAYARAsr5AJ41GMeX34sdShsdyEst2JZm86DgjwCgl69M
9B20BwQXphAYf6mx2ls+jfw=
=s2j3
-----END PGP SIGNATURE-----

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019