Re: Case discrimination

[Ashok Vadekar <avadekar at certicom dot com>]

Thanks.  Now if I can just figure out how to get bash to do file completion of
WIN32 pathnames.  I often am trying to type "word /v/Someth<TAB>" to
commandline launch word with a remote filesystem file whose name I don't
completely know.  Damn windows gui people think that to control document
revisions you have to keep extending the file name ad infinitum.
If I type v:Some<TAB> it doesn't expand.  If I type /v/ and then don't go back
and change /v to v:, word barfs.

On Thu, Jan 25, 2001 at 12:11:07PM -0500, Earnie Boyd wrote:
> Ashok Vadekar wrote:
> > 
> > I looked at the FAQ for case insensitivity of bash, and tried the recommended
> >         shopt -s nocaseglob
> > but it doesn't seem to do what I expected.
> > CD'ed to a directory containing the files "file1" and "File2", I was
> > hoping that typing "ls f<TAB>"
> > would result in expansion only up to the "e", and a further <TAB> would
> > present a list of the two files.  It did not; instead, I got a fully expanded
> > "file1".  Have I got something else wrong, or does the shopt option not do
> > what I was expecting.  If not, is there another method of obtaining this
> > behaviour?
> > 
> 
> echo 'set completion-ignore-case on' > ~/.inputrc
> C-xC-r
> 
> The shopt set shell options where the ~/.inputrc file is for readline
> options.  More documentation `info --file /usr/info/readline'.
> 
> Cheers,
> Earnie.
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple