Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.system > #60299 > unrolled thread
| Started by | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| First post | 2014-06-05 19:18 -0400 |
| Last post | 2014-06-06 02:23 +0000 |
| Articles | 11 — 6 participants |
Back to article view | Back to comp.sys.mac.system
Command line: canse insensitive JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-06-05 19:18 -0400
Re: Command line: canse insensitive Tom Stiller <clusterfux.upmon@gmail.com> - 2014-06-06 00:40 +0000
Re: Command line: canse insensitive Barry Margolin <barmar@alum.mit.edu> - 2014-06-05 21:20 -0400
Re: Command line: canse insensitive JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-06-05 22:35 -0400
Re: Command line: canse insensitive Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-06-06 05:38 +0000
Re: Command line: canse insensitive Jolly Roger <jollyroger@pobox.com> - 2014-06-06 13:54 +0000
Re: Command line: canse insensitive Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-06-06 19:32 +0000
Re: Command line: canse insensitive Darrin "Doc" O'Leary <droleary@2q2014.subsume.com> - 2014-06-06 16:54 +0000
Re: Command line: canse insensitive JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-06-06 13:01 -0400
Re: Command line: canse insensitive Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-06-06 19:33 +0000
Re: Command line: canse insensitive Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-06-06 02:23 +0000
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-06-05 19:18 -0400 |
| Subject | Command line: canse insensitive |
| Message-ID | <5390fabd$0$22380$c3e8da3$f6268168@news.astraweb.com> |
Been reading on on making the command line case insensitive. Mr Google points me to a file called .inputrc which should contain: set completion-ignore-case On However, on Snow Leopard (10.6.9 for those who don't track names :-), inputrc exists neither in the user's login, nor in /etc Anyhow, I found that the "bind" command can make a dynamic change. And it seems to work (by default, "bind -V" reveals it is set to "off" velo:~ $ bind "set completion-ignore-case On" velo:~ $ bind -V ... completion-ignore-case is set to `on' ... yet: velo:~ $ cd /Volumes/DMA2/Apps_dev/crtc/2014-76-may15/ velo:2014-76-may15 $ ls */*.html ls: */*.html: No such file or directory velo:2014-76-may15 $ ls */*.HTML (listing of all the .HTML files) So, obviously, in my ever so slightly different universe, things don't work as expected. Any hints on what to look for ? Also, in which file should the set completion-ignore-case On be put in for Snow Leopard ? Or can I just add the bind version in .bashrc ? Any suggestions would be appreciated.
[toc] | [next] | [standalone]
| From | Tom Stiller <clusterfux.upmon@gmail.com> |
|---|---|
| Date | 2014-06-06 00:40 +0000 |
| Message-ID | <bvch00FttsrU1@mid.individual.net> |
| In reply to | #60299 |
On 2014-06-05, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > Been reading on on making the command line case insensitive. > Mr Google points me to a file called .inputrc which should contain: > set completion-ignore-case On > > However, on Snow Leopard (10.6.9 for those who don't track names :-), > inputrc exists neither in the user's login, nor in /etc > > Anyhow, I found that the "bind" command can make a dynamic change. And > it seems to work (by default, "bind -V" reveals it is set to "off" > > velo:~ $ bind "set completion-ignore-case On" > > velo:~ $ bind -V > ... > completion-ignore-case is set to `on' > ... > > yet: > > velo:~ $ cd /Volumes/DMA2/Apps_dev/crtc/2014-76-may15/ > > velo:2014-76-may15 $ ls */*.html > ls: */*.html: No such file or directory > > velo:2014-76-may15 $ ls */*.HTML > > (listing of all the .HTML files) > > > So, obviously, in my ever so slightly different universe, things don't > work as expected. Any hints on what to look for ? > > Also, in which file should the set completion-ignore-case On be put in > for Snow Leopard ? Or can I just add the bind version in .bashrc ? > > Any suggestions would be appreciated. > I have: ~/.inputrc which contains: set completion-ignore-case On
[toc] | [prev] | [next] | [standalone]
| From | Barry Margolin <barmar@alum.mit.edu> |
|---|---|
| Date | 2014-06-05 21:20 -0400 |
| Message-ID | <barmar-22B10F.21202805062014@news.eternal-september.org> |
| In reply to | #60299 |
In article <5390fabd$0$22380$c3e8da3$f6268168@news.astraweb.com>, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > Been reading on on making the command line case insensitive. > Mr Google points me to a file called .inputrc which should contain: > set completion-ignore-case On > > However, on Snow Leopard (10.6.9 for those who don't track names :-), > inputrc exists neither in the user's login, nor in /etc If it doesn't exist, you create it. > > Anyhow, I found that the "bind" command can make a dynamic change. And > it seems to work (by default, "bind -V" reveals it is set to "off" > > velo:~ $ bind "set completion-ignore-case On" > > velo:~ $ bind -V > ... > completion-ignore-case is set to `on' > ... > > yet: > > velo:~ $ cd /Volumes/DMA2/Apps_dev/crtc/2014-76-may15/ > > velo:2014-76-may15 $ ls */*.html > ls: */*.html: No such file or directory > > velo:2014-76-may15 $ ls */*.HTML > > (listing of all the .HTML files) > > > So, obviously, in my ever so slightly different universe, things don't > work as expected. Any hints on what to look for ? Completion and wildcard expansion are unrelated. Completion is what happens when you start typing a filename, then type TAB to have it automatically finished. To make wildcard expansion case-insensitive, put: shopt -s nocaseglob in your .bashrc -- Barry Margolin, barmar@alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me ***
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-06-05 22:35 -0400 |
| Message-ID | <5391293c$0$2767$c3e8da3$66d3cc2f@news.astraweb.com> |
| In reply to | #60305 |
On 14-06-05 21:20, Barry Margolin wrote: > To make wildcard expansion case-insensitive, put: > > shopt -s nocaseglob > > in your .bashrc Many thanks ! That did the trick ! Learn something new every day !
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-06-06 05:38 +0000 |
| Message-ID | <slrnlp2ku6.1rki.g.kreme@Amelia.local> |
| In reply to | #60305 |
In message <barmar-22B10F.21202805062014@news.eternal-september.org> Barry Margolin <barmar@alum.mit.edu> wrote: > To make wildcard expansion case-insensitive, put: > shopt -s nocaseglob I seem to recall being told this is not a good idea, but I can't remember why. -- showing snuffy is when Sesame Street jumped the shark
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-06-06 13:54 +0000 |
| Message-ID | <bvdvg8F8gltU4@mid.individual.net> |
| In reply to | #60327 |
On 2014-06-06, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote: > In message <barmar-22B10F.21202805062014@news.eternal-september.org> > Barry Margolin <barmar@alum.mit.edu> wrote: >> To make wildcard expansion case-insensitive, put: > >> shopt -s nocaseglob > > I seem to recall being told this is not a good idea, but I can't remember why. I'd try it out and see, but I have no interest in it. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-06-06 19:32 +0000 |
| Message-ID | <slrnlp45ps.1trc.g.kreme@amelia.local> |
| In reply to | #60347 |
In message <bvdvg8F8gltU4@mid.individual.net> Jolly Roger <jollyroger@pobox.com> wrote: > On 2014-06-06, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote: >> In message <barmar-22B10F.21202805062014@news.eternal-september.org> >> Barry Margolin <barmar@alum.mit.edu> wrote: >>> To make wildcard expansion case-insensitive, put: >> >>> shopt -s nocaseglob >> >> I seem to recall being told this is not a good idea, but I can't remember why. > I'd try it out and see, but I have no interest in it. I do like having case insensitive completion, but I never remember to enable it. I suppose I should add .inputrc to the list of files that sync between my accounts. Something about case insensitive globbing scares me though. -- Q: What's the difference between a civil engineer and a military engineer? A: A military engineer designs weapons, and a civil engineer designs targets.
[toc] | [prev] | [next] | [standalone]
| From | Darrin "Doc" O'Leary <droleary@2q2014.subsume.com> |
|---|---|
| Date | 2014-06-06 16:54 +0000 |
| Message-ID | <lmsroq$tj8$1@dont-email.me> |
| In reply to | #60327 |
For your reference, records indicate that Lewis <g.kreme@gmail.com.dontsendmecopies> wrote: > I seem to recall being told this is not a good idea, but I can't remember why. Probably because it could lead to dangerous outcomes, kind of like putting in your search path. It’d also be far better to process files based on their type rather than their extension. (And, yes, I’m deliberately putting . at the start of a line up there to test something out. :-) -- dn ƃuᴉʞool ǝɹɐ sƃuᴉɥʇ
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-06-06 13:01 -0400 |
| Message-ID | <5391f3ff$0$46383$c3e8da3$a9097924@news.astraweb.com> |
| In reply to | #60371 |
> Lewis <g.kreme@gmail.com.dontsendmecopies> wrote: > >> I seem to recall being told this is not a good idea, but I can't remember why. If you are in a case insensitive file system, in what way would allowing wildcarding to also be case insensitive cause problems ? Granted, if you have case sensitive volumes, and your bash is set to be case insensitive, this could cause problem since specifying *.hTMl would get you both chocolate.hTmL and chocolate.html instead of only .hTmL However, on a system that is all case insensitive, NOT making bash case insensitive causes far more problems. I'd like to know why Apple did not make it default to have bash case insensitive.
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-06-06 19:33 +0000 |
| Message-ID | <slrnlp45t0.1trc.g.kreme@amelia.local> |
| In reply to | #60373 |
In message <5391f3ff$0$46383$c3e8da3$a9097924@news.astraweb.com> JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: >> Lewis <g.kreme@gmail.com.dontsendmecopies> wrote: >> >>> I seem to recall being told this is not a good idea, but I can't remember why. > If you are in a case insensitive file system, in what way would allowing > wildcarding to also be case insensitive cause problems ? Like I said, I can't remember. > Granted, if you have case sensitive volumes, and your bash is set to be > case insensitive, this could cause problem since specifying *.hTMl would > get you both chocolate.hTmL and chocolate.html instead of only .hTmL > However, on a system that is all case insensitive, NOT making bash case > insensitive causes far more problems. I'd like to know why Apple did not > make it default to have bash case insensitive. That is a good point. -- 'A man like that could inspire a handful of broken men to conquer a country.' 'Fine. Just so long as he does it on his day off.'
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-06-06 02:23 +0000 |
| Message-ID | <slrnlp29hq.1isd.g.kreme@Amelia.local> |
| In reply to | #60299 |
In message <5390fabd$0$22380$c3e8da3$f6268168@news.astraweb.com> JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > Been reading on on making the command line case insensitive. > Mr Google points me to a file called .inputrc which should contain: > set completion-ignore-case On > However, on Snow Leopard (10.6.9 for those who don't track names :-), > inputrc exists neither in the user's login, nor in /etc Why would you expect it to already exist? > Anyhow, I found that the "bind" command can make a dynamic change. And > it seems to work (by default, "bind -V" reveals it is set to "off" Are you incapable of following simple instructions? > velo:2014-76-may15 $ ls */*.html > ls: */*.html: No such file or directory > velo:2014-76-may15 $ ls */*.HTML Yes? And? This has nothing at all to do with completion. > So, obviously, in my ever so slightly different universe, things don't > work as expected. Any hints on what to look for ? A clue? A primer on reading comprehension? > Also, in which file should the set completion-ignore-case On be put in > for Snow Leopard ? Or can I just add the bind version in .bashrc ? Where you already given those instructions? > Any suggestions would be appreciated. See above. -- When the stars threw down their spears And watered heaven with their tears, Did He smile his work to see? Did He who made the Lamb make thee?
[toc] | [prev] | [standalone]
Back to top | Article view | comp.sys.mac.system
csiph-web