Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
