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
en:utility-scripts:chttl [2025/01/06 06:56] – [Make it a function] Webmaster VitaNetworksen:utility-scripts:chttl [2025/01/06 07:46] (current) – Webmaster VitaNetworks
Line 10: Line 10:
  
 ===== Is there something else? ===== ===== Is there something else? =====
-- This is the first [intentionaly] POSIX-compliant script we've ever written. +- This is the first [intentionaly] POSIX-compliant script we've ever written.\\  
-- It works on macOS, Linux and FreeBSD. +- It works on macOS, Linux and FreeBSD.\\  
-- It can be used to set the value back to where it was as well, simply add it at the end. +- It can be used to set the value back to where it was as well, simply add it at the end.\\  
-- It's not a permanent modification. +- It's not a permanent modification.\\  
-  Depending on the OS, you might need to create a file in a specific location or issue a special command that sets preference files.+  - Depending on the OS, you might need to create a file in a specific location or issue a special command that sets preference files.
  
 ==== Make it a function ==== ==== Make it a function ====
-This was originally written as a bash function. It was changed early on to ''sh'' for portability reasons but nevertheless it was wrapped in a single unit to make it easy to change it back. +This was originally written as a bash function. It was changed early on to ''sh'' for portability reasons but nevertheless it was wrapped in a single unit to make it easy to change it back. All you need is to remove the shebang (first) line and the call out or invocation (last) line from the script. Then paste the remainder of the code in your bash functions file(s).
- +
-You only need to remove the shebang (first) line and the call out or invocation (last) line from the script. Then paste the remainder of the code in your bash functions file(s).+
  
 === Using a functions file === === Using a functions file ===
Line 27: Line 25:
 - ''~/.bash_login'', and - ''~/.bash_login'', and
 - ''~/.profile'', - ''~/.profile'',
-Typically ''~/.bash_profile'' would call ''~/.bashrc'' which will be executed every single new CLI session. i.e; +Typically ''~/.bash_profile'' would call ''~/.bashrc'' which will be executed every single new CLI session. i.e;\\  
-<code>if [ -f ~/.bashrc ]; then . ~/.bashrc; fi</code> +''if [ -f ~/.bashrc ]; then . ~/.bashrc; fi''\\  
-Meaning "//if ''~/.bashrc'' exists, run it// ".+(meaning "//if ''~/.bashrc'' exists, run it// ".)
  
-You may follow the bash's own example and create a file such as ''~/bin/bashfunctions'' and call it from ''~/.bash_profile'', so it lives with your scripts, assuming that's where you'll keep them and you have a much easier job syncing things across systems, e.g;+You may follow the bash's own example by invoking the functions file from ''~/.bash_profile'' e.g; ''if [ -f "${HOME}/bin/bashfunctions" ]; then . "${HOME}/bin/bashfunctions"; fi'' where the file was created to live alongside your scritps on ''"${HOME}/bin"'' and it would be a much easier job syncing things across systems.
 <code> <code>
 [Sun05@23:20:52][vuser@vpro:~] $〉ls [Sun05@23:20:52][vuser@vpro:~] $〉ls
Line 37: Line 35:
  24 -rw-------    1 vuser  vgroup    12K Jan  5 23:04 .bash_history  24 -rw-------    1 vuser  vgroup    12K Jan  5 23:04 .bash_history
   8 -rw-r-xr-x@   1 vuser  vgroup   1.7K Oct 25 16:51 .bash_profile*   8 -rw-r-xr-x@   1 vuser  vgroup   1.7K Oct 25 16:51 .bash_profile*
 +########################################################################################################
 +#↑↑↑ Add 'if [ -f "${HOME}/bin/bashfunctions" ]; then . "${HOME}/bin/bashfunctions"; fi'            ↑↑↑#
 +########################################################################################################
   8 -rw-r--r--    1 vuser  vgroup   1.5K Jul  3  2024 .bash_profile.bak   8 -rw-r--r--    1 vuser  vgroup   1.5K Jul  3  2024 .bash_profile.bak
   8 -rw-r-xr-x@   1 vuser  vgroup   1.1K Mar 27  2024 .bash_profile.pysave*   8 -rw-r-xr-x@   1 vuser  vgroup   1.1K Mar 27  2024 .bash_profile.pysave*
Line 42: Line 43:
  16 -rw-r-xr-x@   1 vuser  vgroup   4.7K Oct 14 16:01 .bashrc*  16 -rw-r-xr-x@   1 vuser  vgroup   4.7K Oct 14 16:01 .bashrc*
   0 drwxr-xr-x  172 vuser  vgroup   5.4K Jan  5 16:18 bin/   0 drwxr-xr-x  172 vuser  vgroup   5.4K Jan  5 16:18 bin/
 +
 [Sun05@23:50:41][vuser@vpro:~] $〉ls bin [Sun05@23:50:41][vuser@vpro:~] $〉ls bin
 total n total n
Line 51: Line 53:
    8 -rwxr-xr-x   1 vuser  vgroup   2.6K Oct 18 13:02 bashaliases*    8 -rwxr-xr-x   1 vuser  vgroup   2.6K Oct 18 13:02 bashaliases*
   16 -rwxr-xr-x@  1 vuser  vgroup   6.8K Jan  5 00:10 bashfunctions*   16 -rwxr-xr-x@  1 vuser  vgroup   6.8K Jan  5 00:10 bashfunctions*
 +########################################################################################################
 +#↑↑↑         Functions file example                                                                 ↑↑↑#
 +########################################################################################################
    8 -rwxr-xr-x   1 vuser  vgroup   3.5K Nov  1 17:20 bashvars*    8 -rwxr-xr-x   1 vuser  vgroup   3.5K Nov  1 17:20 bashvars*
    8 -rwxr-xr-x   1 vuser  vgroup    30B May  1  2022 catprivkey*    8 -rwxr-xr-x   1 vuser  vgroup    30B May  1  2022 catprivkey*