User Tools

Site Tools

tools:bash:customization

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
tools:bash:customization [2024/06/04 02:45] – [Other Codes] Humphrey Boa-Garttools:bash:customization [2025/01/04 03:40] (current) – Humphrey Boa-Gart
Line 40: Line 40:
 As you start to use bash more often, you will find yourself using specific combinations of commands and flags to accomplish basic tasks. You can drastically cut the amount of typing you will do by setting **aliases**, which are just pseudo-commands that refer to other commands. These are the simplest customizations to make to bash. As you start to use bash more often, you will find yourself using specific combinations of commands and flags to accomplish basic tasks. You can drastically cut the amount of typing you will do by setting **aliases**, which are just pseudo-commands that refer to other commands. These are the simplest customizations to make to bash.
  
-For example, lets look at the ''ls'' command. The default output of ls is very bare-bones, and you have to type something like ''ls -lhaF'' to get a more detailed view. To make it so typing ''ls'' by itself gives you an easy-to-read detail view, add the following line to your **.bash_aliases** file:+For example, lets look at the ''ls'' command. The default output of ls is very bare-bones, and you have to type something like ''ls -lhAF'' to get a more detailed view. To make it so typing ''ls'' by itself gives you an easy-to-read detail view, add the following line to your **.bash_aliases** file:
  
-  ls='ls -lhaF --color=auto'+  ls='ls -lhAF --color=auto'
  
 Aliases do not have to be permanent, either. To set that same alias to only work for the current shell session, you would run: Aliases do not have to be permanent, either. To set that same alias to only work for the current shell session, you would run:
  
-  $ alias ls=\'ls -lhaF --color=auto\'+  $ alias ls=\'ls -lhAF --color=auto\'
  
 To unset that alias, you would run: To unset that alias, you would run:
Line 72: Line 72:
   PS1='\[\033[01;32m\]\u@\h\[\033[00m\] \[\033[01;34m\]\w\[\033[00m\] \[\033[01;32m\]\$\[\033[00m\] '   PS1='\[\033[01;32m\]\u@\h\[\033[00m\] \[\033[01;34m\]\w\[\033[00m\] \[\033[01;32m\]\$\[\033[00m\] '
  
-Here is a <wrap em>red version</wrap> of the same prompt, which you can add to the aliases file for a root user or superuser, so you can more easily tell at a glance when you are in an account with escalated privs:+Here is a separate <wrap em>red version</wrap> of the same prompt, which you can add to the aliases file for a root user or superuser, so you can more easily tell at a glance when you are in an account with escalated privs:
  
   PS1='\[\033[01;31m\]\u@\h\[\033[00m\] \[\033[01;34m\]\w\[\033[00m\] \[\033[01;31m\]\$\[\033[00m\] '   PS1='\[\033[01;31m\]\u@\h\[\033[00m\] \[\033[01;34m\]\w\[\033[00m\] \[\033[01;31m\]\$\[\033[00m\] '
Line 104: Line 104:
   /home/user/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin   /home/user/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
      
-This above line shows that bash will look in your personal **~/.local/bin** directory, as well as a list of common locations for globally-accessible binaries. Your system may have other locations appended here as well for things like games, [[tools:flatpak|Flatpak]] or [[tools:snap|Snap]].+This above line shows that bash will look in your personal **~/.local/bin** directory, as well as a list of common locations for globally-accessible binaries. Your system may have other locations appended here as well for things like games, [[tools:flatpak|Flatpak]] or [[tools:flatpak#snap|Snap]].
  
 To enable bash to run a custom application (such as a freshly downloaded [[tools:appimage|AppImage]] file) without having to type out the whole directory it is located in, you should place the file into your personal **~/.local/bin** directory. Or, you could put a symlink into that directory like so: To enable bash to run a custom application (such as a freshly downloaded [[tools:appimage|AppImage]] file) without having to type out the whole directory it is located in, you should place the file into your personal **~/.local/bin** directory. Or, you could put a symlink into that directory like so:
Line 202: Line 202:
 ===== ANSI Escape Codes ===== ===== ANSI Escape Codes =====
  
-When you set your custom hostname earlier in this article, you may have noticed a bunch of numbers on your new $PS1 line. Those are **ANSI Escape Codes** which you can use to tweak the style of bash output. You have a range of codes available:+When you set your custom hostname earlier in this article, you may have noticed the **\033[..m]** or **\033[..;..m]** blocks, which contain a semicolon-separated list of other numbers with an **m**. Those **"m"** numbers are **ANSI Escape Codes** which you can use to tweak the style of bash output. You have a range of codes available:
  
 ==== Color Codes ==== ==== Color Codes ====
Line 227: Line 227:
  
 ^ Code ^ Description     ^ ^ Code ^ Description     ^
-| 0    | Reset/Normal    | +| 00   | Reset/Normal    | 
-| 1    | Bold text       | +| 01   | Bold text       | 
-| 2    | Faint text      | +| 02   | Faint text      | 
-| 3    | Italics         | +| 03   | Italics         | 
-| 4    | Underlined text |+| 04   | Underlined text | 
 + 
  
 ---- ----
  
 +  * Previous Page: [[tools:bash:files-archives|← Managing Files & Archives]]
   * [[tools:bash|Back to Index]]   * [[tools:bash|Back to Index]]
 +
 +
 +{{wst>cli}}
tools/bash/customization.1717469135.txt.gz · Last modified: 2024/08/06 05:54 (external edit)

Find this page online at: https://bestpoint.institute/tools/bash/customization