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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Does anyone no how I can clear the history of my command prompt. I usually use the repeat function when programming, but now I have a bunch of other commands in between so it's not as convenient.
Just so I'm not confusing. When at the command prompt, I can push the up arrow to scroll through past entered commands. But there is a history of weeks of mistype and deleted files, can I clear that history?
you can just delete the ~/.bash_history file for a one of shot over logout. you can also set the HISTSIZE option to a lower value in your .bashrc to reduce the number of saved commands, or add "unset HISTFILE" to not save it to disk at all.
Here are two more shell variable options for you to help keep your history sane.
Use "HISTCONTROL=ignoredups" to keep the history from recording multiple instances of the same command, or use "erasedups" instead to keep only the most recent entry.
And using "HISTIGNORE=colon:separated:list:of:commands" will make it ignore any commands that you don't want to see at all.
There are more options you can use. Check out the bash man page.
Edit: here's one more that I use often--history searching. Hitting crtl+r, then typing something will bring up the most recent matching string in your history. Hit it again for the next match, or crtl+s to move forward again. Makes it easy to jump back to previously-used commands.
Last edited by David the H.; 11-13-2008 at 09:12 AM.
Here are two more shell variable options for you to help keep your history sane.
Use "HISTCONTROL=ignoredups" to keep the history from recording multiple instances of the same command, or use "erasedups" instead to keep only the most recent entry.
And using "HISTIGNORE=colon:separated:list:of:commands" will make it ignore any commands that you don't want to see at all.
There are more options you can use. Check out the bash man page.
Edit: here's one more that I use often--history searching. Hitting crtl+r, then typing something will bring up the most recent matching string in your history. Hit it again for the next match, or crtl+s to move forward again. Makes it easy to jump back to previously-used commands.
Another "goodie" in this context is how to handle
the ~/.bash_history if you have several terminals
open and use them all intermittently (wanting to
retain the history in one big file):
Code:
# handle history file gracefully for multiple windows open
shopt -s histappend
export PROMPT_COMMAND='history -a'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.