[SOLVED] Missing characters in xterm after customizing local .bashrc file.
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.
Missing characters in xterm after customizing local .bashrc file.
Hi,
I running Slackware v14 and learning how to customize my xterm by editing my local .bashrc file.
The only two entries I have in the file are:
Code:
PS1="[\T](\u) \W \$ "
export PS1
When I start up xterm, the prompt has changed as expected but I'm unable to enter the characters 'P' and 'e' in the terminal. If I delete the two entries and restart the terminal using the default configuration file, I'm able to key in all of the characters.
I running Slackware v14 and learning how to customize my xterm by editing my local .bashrc file.
The only two entries I have in the file are:
Code:
PS1="[\T](\u) \W \$ "
export PS1
When I start up xterm, the prompt has changed as expected but I'm unable to enter the characters 'P' and 'e' in the terminal. If I delete the two entries and restart the terminal using the default configuration file, I'm able to key in all of the characters.
What's causing this and how do fix it?
TIA
Shouldn't be any problem with it. I put it at the end of my .bashrc and it works fine, P and e and all other letters as normal. I'm using slackware 13.37. The only thing I can think of is that it may be related to slackware 14. Try asking on the slackware forum.
I running Slackware v14 and learning how to customize my xterm by editing my local .bashrc file.
The only two entries I have in the file are:
Code:
PS1="[\T](\u) \W \$ "
export PS1
When I start up xterm, the prompt has changed as expected but I'm unable to enter the characters 'P' and 'e' in the terminal. If I delete the two entries and restart the terminal using the default configuration file, I'm able to key in all of the characters.
What's causing this and how do fix it?
TIA
I'm running Slackware 14 RC 4 and when I put this in my .bashrc it works fine. I am able to enter the characters P and e. Unfortunately I can't help with the problem but hopefully this might help narrow something down for you. Good luck!
is giving you problems. It work fine when it tried. Alright try putting it elsewhere i.e. your home bash profile or the root bashrc file or root profile. see if if you still experience the problem.
I have found that the bash prompt is very sensitive, i.e. one PS1 string will mostly work but a slight change can have drastic consequences. For example, I formatted my prompt with:
Which looked like what I had in mind, but somethings didn't feel right such as line wrapping on large commands. I surrounded each item in straight braces [ ], to yield:
My point is that there are many solutions to your target. Small changes can have large impacts. I suggest trying single quotes in your PS1 string instead of double quotes.
Last edited by Obscurious; 09-13-2012 at 04:12 PM.
Try enclosing the value assigned to PS1 in single quotes. There is no purpose to allowing the shell to interpret anything in the string before it is assigned. There are some 'special' characters in the string which might be interpreted/expanded by the shell, which isn't what you want. If you echo $PS1, it should reveal any such translations. Also, type set which may reveal any aliases or functions that might be silently participating in some meddling with the terminal.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.