bash questions

i92guboj · 02-19-2010, 11:07 AM

Quote:

Originally Posted by schneidz

i never use capitals either (its just an extraneous keystroke).

when i was in college we created a my-shell program in lab.

I have no idea what college did you go to. In mine, for sure, I wouldn't have obtained a degree if I hadn't respected the basic orthographic rules of my mother language. Just like you can't bypass the rules in C either.

Quote:

case-insensitivity can theoretically be done with something like tr [A-Z] [a-z] but it would likely hinder more than it would help.

True case insensitivity is simply not possible without hacking at core level, starting with glibc. Then you would need to patch 99% of the user land applications so they don't get confused.

You can try to stay caseless for your personal files, but you need to have in mind always that your system doesn't think that way. You will understand that the day you need to edit /etc/X11/xorg.conf but you edited /etc/x11/xorg.conf, for example. Lots of time will be wasted just because you refuse to learn a basic rule.

I personally don't care if you or the OP do or not acknowledge this. I am just exposing the facts, and facts are that all the unix clones (including linux) are case sensitive to the bone. It's nothing that a shell or a single program or tool can fix without massively patching all the components of your system

schneidz · 02-19-2010, 11:11 AM

^ damn, sorry i offended you.

GrapefruiTgirl · 02-19-2010, 11:18 AM

Quote:

Originally Posted by i92guboj

echo 'set completion-ignore-case on' > ~/.inputrc

Not to get off topic here hopefully, but @ Jêsus -- since you mentioned ~/.inputrc I want to ask:

When I look into my /etc/profile file, wherein the INPUTRC environment variable is set, there is a test like:

if ~/.inputrc exists, use that; else use /etc/inputrc

So, the question: is there a provision in readline whereby it will use BOTH files? Or, if I want to have some special stuff in my ~/.inputrc, then I should first copy /etc/inputrc to ~/.inputrc because readline can/will only use one or the other file?

The readline man page didn't say whether multiple files would be considered.

Cheers,
Sasha

i92guboj · 02-19-2010, 11:48 AM

Hi, Sasha.

Quote:

Originally Posted by GrapefruiTgirl

Not to get off topic here hopefully, but @ Jêsus -- since you mentioned ~/.inputrc I want to ask:

When I look into my /etc/profile file, wherein the INPUTRC environment variable is set, there is a test like:

if ~/.inputrc exists, use that; else use /etc/inputrc

That's unnecessary (redundant) anyway. Since it's the default behavior of readline itself.

Quote:

So, the question: is there a provision in readline whereby it will use BOTH files? Or, if I want to have some special stuff in my ~/.inputrc, then I should first copy /etc/inputrc to ~/.inputrc because readline can/will only use one or the other file?

As far as I know, the first file that's found will be used. The precedence order gives the ~/.inputrc file the highest priority, over /etc/inputrc.

However, you can use "$include /etc/inputrc" in your ~/.inputrc file, so you don't need to copy the file, and you will stay in sync with whatever the system updates put there.

GrapefruiTgirl · 02-19-2010, 11:50 AM

Quote:

However, you can use "$include /etc/inputrc" in your ~/.inputrc file

Ahh!

That's just the perfect thing right there. Thank you!

Sasha