Differences

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

--- tools:bash:customization [2024/06/04 01:43] – Humphrey Boa-Gart
+++ tools: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.
-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:
-  $ alias ls=\'ls -lhaF --color=auto\'
+  $ alias ls=\'ls -lhAF --color=auto\'
 To unset that alias, you would run:
@@ Line 59: / Line 59: @@
   $ alias -p
+===== More Simple Tricks =====
+You can set all sorts of things up in your aliases file. The following are just a few tweaks you can make:
+==== Custom Hostnames ====
+You can tweak the prompt, aka the string that appears before $ in your terminal. (Usually something like **[user@host]$**)
+If you want to restyle the prompt, you will need to set it to the **$PS1** variable. Here is one example with custom green and blue color codes, which you can copy/paste to your aliases file and use right away:
+  PS1='\[\033[01;32m\]\u@\h\[\033[00m\] \[\033[01;34m\]\w\[\033[00m\] \[\033[01;32m\]\$\[\033[00m\] '
+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\] '
+Be careful setting the **$PS1** variable, as you can very easily make your shell unusable if you set it the wrong way!
+//(See 'ANSI Escape Codes' at the bottom of this page for more color options.)//
+==== Harden umask ====
+By default your **umask** is probably set up to give read access to things that do not need it by default. To make it so all new files/folders you create are chmodded to 600/700, add the following line to your aliases file:
+  umask 0077
+//(See [[tools:bash:users-permissions#umask|Part 4: Users and Permissions]] for more info.)//
 ===== Environment Variables =====
@@ Line 76: / Line 104: @@
   /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 [[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:
@@ Line 171: / Line 199: @@
   * Export and unset, when used in a child shell, will not affect the parent shell.
   * Variable arrays start with an index value of zero, not one.
+===== ANSI Escape Codes =====
+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         ^ Foreground Code ^ Background Code ^
+| Black         | 30              | 40              |
+| Red           | 31              | 41              |
+| Green         | 32              | 42              |
+| Yellow        | 33              | 43              |
+| Blue          | 34              | 44              |
+| Magenta       | 35              | 45              |
+| Cyan          | 36              | 46              |
+| Light Gray    | 37              | 47              |
+| Gray          | 90              | 100             |
+| Light Red	| 91      	  | 101             |
+| Light Green	| 92      	  | 102             |
+| Light Yellow	| 93      	  | 103             |
+| Light Blue	| 94      	  | 104             |
+| Light Magenta | 95              | 105             |
+| Light Cyan	| 96      	  | 106             |
+| White    	| 97      	  | 107             |
+==== Other Codes ====
+^ Code ^ Description     ^
+| 00   | Reset/Normal    |
+| 01   | Bold text       |
+| 02   | Faint text      |
+| 03   | Italics         |
+| 04   | Underlined text |
 ----
+  * Previous Page: [[tools:bash:files-archives|← Managing Files & Archives]]
   * [[tools:bash|Back to Index]]
+{{wst>cli}}

User Tools

Site Tools

Differences