Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
First of all, I'm not a bash user so keep your comments at bay my friends.
My buddy is a bash user and has been experiencing an interesting problem lately: the lowercase 'b' does not show up in a terminal window! All other letters, upper and lowercase do, and the lowercase b works everywhere else...even when editing in vi from a terminal! Go figure! He used to be able to copy/paste a 'b' onto the command line but even that doesn't work now. The only time we can get a 'b' to show up is when using forward (tab) completion of a file/directory/app which contains one...but never one that BEGINS with it.
So, since I'm always giving him a ration of crap for being a bash user I exclaimed, "Yeah, it's probably because you're a bash user!" On that note, he logged into a cshell and viola...the letter 'b' works just fine?! Are you kidding me?
It's definitely not a finicky hardware problem...that's been ruled out. It's not a system-wide problem because the keystroke works when using vi in a terminal window and in other apps as well.
Has anyone seen/heard of this before? The easy work around is to just have him switch to csh or tcsh, but an explanation or conjecture would be amusing. By the way, it's RedHat Enterprise Linux (2.4.21-27.0.2.EL).
I believe that both vi and bash use the readline library, so that would rule out a problem with the readline key definitions.
There is a bash builtin command called bind that might be the culprit. Perhaps there is something in one of the bash startup files to uses it. The only other thing I can think of is if he is using a font-encoding that is incompete. Such as a sample font, or one extracted from a pdf file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.