User Tools

(aka 'the best point military institute')

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:59] – [Custom Hostnames] Humphrey Boa-Garttools:bash:customization [2026/03/08 09:12] (current) – [$PATH] Humphrey Boa-Gart
Line 96: Line 96:
 ==== $PATH ==== ==== $PATH ====
  
-The most important variable you will deal with, is the **$PATH** variable, which specifies the directories that bash will look for executable files. (So you can type ''appname'' instead of ''/path/to/appname'' into your shell to run the program.) To figure out where your $PATH is, run:+The most important variable you will deal with, is the **$PATH** variable, which specifies the directories that bash will look for installed applications. This lets you type ''appname'' into your shell to run a program, instead of a drawn out path like ''/path/to/appname''. If the directory is not in your $PATH, then bash will not know to look there for apps. 
 + 
 +To figure out where your $PATH is, run:
  
   $ echo $PATH   $ echo $PATH
Line 102: Line 104:
 This will output something like: This will output something like:
  
-  /home/user/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin+  /home/username/.local/bin:/usr/local/bin:/usr/bin:/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)//, you should place the file into your personal **~/.local/bin** directory //(which will almost-always be in your $PATH by default on modern systems)//. Or, you could put a symlink into that directory like so:
  
   $ ln -s /path/to/the.appimage ~/.local/bin/commandname   $ ln -s /path/to/the.appimage ~/.local/bin/commandname
Line 233: Line 235:
 | 04   | Underlined text | | 04   | Underlined text |
  
----- 
  
-  * [[tools:bash|Back to Index]]+ 
 +{{wst>cli}} 
tools/bash/customization.1717469987.txt.gz · Last modified: (external edit)

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