RE: completion-ignore-case problem with cygwin

["Levy, Bruce" <blevy@qualcomm.com>]

Hi Eric,

Thank you (and Igor) for the help.  I have created a Windows Environment
Variable that points to .inputrc.  That has fixed the problem.  Your
suggestion (and Igor's) about checking the setting of HOME has gotten me
to clean up my startup files.  I got rid of my old ones and used the
ones in /etc/defaults/etc/skel.  My startup process is now much cleaner
and one that I can maintain.

I very much appreciate the help.

Best Wishes,
Bruce


-----Original Message-----
From: Eric Blake [mailto:ebb9@byu.net] 
Sent: Friday, September 15, 2006 4:45 AM
To: cygwin@cygwin.com; Levy, Bruce
Subject: Re: completion-ignore-case problem with cygwin


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.


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