Editing Bash (Unix shell) (section)

== Documentation ==
As the standard upon which bash is based, the POSIX Standard, or IEEE Std 1003.1,<ref>{{Cite web |title=The Open Group Base Specifications Issue 7, 2018 edition     |url=https://pubs.opengroup.org/onlinepubs/9699919799/     |website=pubs.opengroup.org  }}</ref> et seq, is especially informative.

The Linux "man page"<ref>{{Cite web |title=BASH(1) Manual Page     |url=https://tiswww.case.edu/php/chet/bash/bash.html     |website=tiswww.case.edu  }}</ref><ref>{{Cite web |title=bash.0\doc - bash.git - bash     |url=https://git.savannah.gnu.org/cgit/bash.git/tree/doc/bash.0     |via=git.savannah.gnu.org  }}</ref> is intended to be the authoritative explanatory technical document for the understanding of how <code>bash</code> operates. It is usually available by running <code>man bash</code>.

The GNU [https://www.gnu.org/software/bash/manual/index.html manual] is sometimes considered more user-friendly for reading. "You may also find information about Bash by running <code>info bash</code> ... or by looking at <code>/usr/share/doc/bash/</code>, <code>/usr/local/share/doc/bash/</code>, or similar directories on your system.  A brief summary is available by running <code>bash --help</code>.<ref name="auto">{{Cite web |title=Bash |publisher=GNU Project  |url=https://www.gnu.org/savannah-checkouts/gnu/bash/bash.html     |access-date=2024-01-10}}</ref>

" If a user invoke RUNCOM without any arguments it prints some instructions on how to use it and stops, returning the user to the supervisor's (system's) command line.([[RUNCOM]])"

On modern Linuxes, information on shell built-in commands can be found by executing <code>help</code>, <code>help [built-in name]</code> or <code>man builtins</code> at a terminal prompt where bash is installed. Some commands, such as <code>echo</code>, <code>false</code>, <code>kill</code>, <code>printf</code>, <code>test</code> or <code>true</code>, depending on your system and on your locally installed version of bash, can refer to either a shell built-in or a system binary executable file. When one of these command name collisions occurs, bash will by default execute a given command line using the shell built-in. Specifying a binary executable's absolute path (i.e., <code>/bin/printf</code>) is one way of ensuring that the shell uses a system binary. This name collision issue also effects any "help summaries" viewed with <code>kill --help</code> and <code>/bin/kill --help</code>. Shell built-ins and system binary executable files of the same name often have differing options.

"The project maintainer also has a Bash page which includes Frequently Asked Questions",<ref>{{multiref|
  {{Cite web |title=The GNU Bourne-Again Shell     |url=https://tiswww.case.edu/php/chet/bash/bashtop.html     |website=tiswww.case.edu  }}
|
  {{ cite web
    | title = Frequently Asked Questions
    | url = https://tiswww.case.edu/php/chet/bash/FAQ
    | website = tiswww.case.edu
  }}
}}</ref><ref name="auto" /> this FAQ is current as of bash version 5.1 and is no longer updated.