[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
slackbook:bash [2012/09/08 18:05 (UTC)] – [Terminals] updated section to match original with formatting mfillpotslackbook:bash [2012/09/08 18:10 (UTC)] – [Sources] updated author list mfillpot
Line 342: Line 342:
 ===== Customization ===== ===== Customization =====
  
-By now you should be pretty familiar with bash and you may have even noticed some odd behavior. For example, when you login at the console, you're presented with a prompt that looks a bit like this.+By now you should be pretty familiar with 
 +**//bash//** and you may have even noticed some odd 
 +behavior. For example, when you login at the console, you're presented 
 +with a prompt that looks a bit like this. 
  
 <code> <code>
-alan@darkstar:~$  +alan@darkstar:~$ </code> 
-</code>+ 
 However, sometimes you'll see a much less helpful prompt like this one. However, sometimes you'll see a much less helpful prompt like this one.
 +
  
 <code> <code>
-bash-3.1$  +bash-3.1$ </code> 
-</code>+ 
 + 
 +The cause here is a special environment variable that controls the 
 +**//bash//** prompt. Some shells are considered 
 +//"login"// shells and others are //"interactive"// shells, and both types read 
 +different configuration files when started. Login shells read 
 +''/etc/profile'' and 
 +''~/.bash_profile'' when executed. Interactive shells 
 +read ''~/.bashrc'' instead. This has some advantages 
 +for power users, but is a common annoyance for many new users who want 
 +the same environment anytime they execute 
 +**//bash//** and don't care about the difference 
 +between login and interactive shells. If this applies to you, simply 
 +edit your own ~/.bashrc file and include the following lines. 
 +(For more information on 
 +the different configuration files used, read the INVOCATION section of 
 +the **//bash//** man page.)
  
-The cause here is a special environment variable that controls the bash prompt. Some shells are considered "login" shells and others are "interactive" shells, and both types read different configuration files when started. Login shells read /etc/profile and ~/.bash_profile when executed. Interactive shells read ~/.bashrc instead. This has some advantages for power users, but is a common annoyance for many new users who want the same environment anytime they execute bash and don't care about the difference between login and interactive shells. If this applies to you, simply edit your own ~/.bashrc file and include the following lines. (For more information on the different configuration files used, read the INVOCATION section of the bash man page.) 
  
 <code> <code>
 +
 # ~/.bashrc # ~/.bashrc
 . /etc/profile . /etc/profile
Line 361: Line 383:
 </code> </code>
  
-When using the above, all your login and interactive shells will have the same environment settings and behave identically. Now, anytime we wish to customize a shell setting, we only have to edit ~/.bash_profile for user-specific changes and /etc/profile for global settings. Let's start by configuring the prompt. 
  
-bash prompts come in all shapes, colors, and sizes, and every user has their own preferances. Personally, I prefer short and simple prompts that take up a minimum of space, but I've seen and used mutli-line prompts many times. One personal friend of mine even included ASCII-art in his bash prompt. To change your prompt you need only to change your PS1 variable. By default, Slackware attempts to configure your PS1 variable thusly:+When using the above, all your login and interactive shells will have 
 +the same environment settings and behave identically. Now, anytime we 
 +wish to customize a shell setting, we only have to edit 
 +''~/.bash_profile'' for user-specific changes and 
 +''/etc/profile'' for global settings. Let's start by 
 +configuring the prompt. 
 + 
 + 
 +**//bash//** prompts come in all shapes, colors, and 
 +sizes, and every user has their own preferances. Personally, I prefer 
 +short and simple prompts that take up a minimum of space, but I've seen 
 +and used mutli-line prompts many times. One personal friend of mine 
 +even included ASCII-art in his bash prompt. To change your prompt you 
 +need only to change your PS1 variable. By default, Slackware attempts 
 +to configure your PS1 variable thusly: 
  
 <code> <code>
 darkstar:~$ echo $PS1 darkstar:~$ echo $PS1
-\u@\h:\w\$  +\u@\h:\w\$ </code>
-</code>+
  
-Yes, this tiny piece of funny-looking figures controls your bash prompt. Basicaly, every character in the PS1 variable is included in the prompt, unless it is a escaped by a \, which tells bash to interpret it. There are many different escape sequences and we can't discuss them all, but I'll explain these. The first "\u" translates to the username of the current user. "\h" is the hostname of the machine the terminal is attached to. "\w" is the current working directory, and "\$" displays either a # or a $ sign, depending on whether or not the current user is root. A complete listing of all prompt escape sequences is listed in the bash man page under the PROMPTING section. 
  
-Since we've gone through all this trouble to discuss the default prompt, I thought I'd take some time to show you a couple example prompts and the PS1 variable values needed to use them.+Yes, this tiny piece of funny-looking figures controls your 
 +**//bash//** prompt. Basicaly, every character in 
 +the PS1 variable is included in the prompt, unless it is a escaped by a 
 +<key>\</key>, which tells **//bash//** to 
 +interpret it. There are many different escape sequences and we can't 
 +discuss them all, but I'll explain these.  The first //"\u"// translates to 
 +the username of the current user.  //"\h"// is the hostname of the machine 
 +the terminal is attached to. //"\w"// is the current working directory, and 
 +//"\$"// displays either a <key>#</key> or a <key>$</key> sign, 
 +depending on whether or not the current user is root.  A complete 
 +listing of all prompt escape sequences is listed in the 
 +**//bash//** man page under the PROMPTING section. 
 + 
 + 
 +Since we've gone through all this trouble to discuss the default 
 +prompt, I thought I'd take some time to show you a couple example 
 +prompts and the PS1 variable values needed to use them. 
  
 <code> <code>
Line 383: Line 434:
 </code> </code>
  
-For even more information on configuring your bash prompt, including information on setting up colored prompts, refer to /usr/doc/Linux-HOWTOs/Bash-Prompt-HOWTO. After reading that for a short while, you'll get an idea of just how powerful your bash prompts can be. I once even had a prompt that gave me up to date weather information such as temperature and barometric pressure! 
  
 +For even more information on configuring your bash prompt, including
 +information on setting up colored prompts, refer to
 +''/usr/doc/Linux-HOWTOs/Bash-Prompt-HOWTO''. After
 +reading that for a short while, you'll get an idea of just how powerful
 +your **//bash//** prompts can be. I once even had a
 +prompt that gave me up to date weather information such as temperature
 +and barometric pressure!
 +
 +====== Chapter Navigation ======
 +
 +**Previous Chapter: [[slackbook:shell|Basic Shell Commands]]**
 +
 +**Next Chapter: [[slackbook:process_control|Process Control]]**
 ====== Sources ====== ====== Sources ======
 <!-- If you copy information from another source, then specify that source --> <!-- If you copy information from another source, then specify that source -->
- * Original source: [[http://www.slackbook.org/beta/#ch_bash]] + * Original source: [[http://www.slackbook.org/beta]] \\
 <!-- Authors are allowed to give credit to themselves! --> <!-- Authors are allowed to give credit to themselves! -->
-<!-- * Originally written by [[wiki:user:xxx | User X]] -->+ * Originally written by Alan Hicks, Chris Lumens, David Cantrell, Logan Johnson
 <!-- * Contrbutions by [[wiki:user:yyy | User Y]] --> <!-- * Contrbutions by [[wiki:user:yyy | User Y]] -->
  

Trace:

slackbook:bash ()