mirror of
https://github.com/fish-shell/fish-shell
synced 2024-12-27 21:33:09 +00:00
docs/index: update some formatting from #9482
(cherry picked from commit e20d78431b
)
This commit is contained in:
parent
308e0ceb9d
commit
d0f1d5e595
1 changed files with 2 additions and 2 deletions
|
@ -107,11 +107,11 @@ If you want to share your script with others, you might want to use :command:`en
|
|||
#!/usr/bin/env fish
|
||||
echo Hello from fish $version
|
||||
|
||||
This will call ``env``, which then goes through :envvar:`PATH` to find a program called "fish". This makes it work, whether fish is installed in /usr/local/bin/fish or /usr/bin/fish or ~/.local/bin/fish, as long as that directory is in :envvar:`PATH`.
|
||||
This will call ``env``, which then goes through :envvar:`PATH` to find a program called "fish". This makes it work, whether fish is installed in (for example) ``/usr/local/bin/fish``, ``/usr/bin/fish``, or ``~/.local/bin/fish``, as long as that directory is in :envvar:`PATH`.
|
||||
|
||||
The shebang line is only used when scripts are executed without specifying the interpreter. For functions inside fish or when executing a script with ``fish /path/to/script``, a shebang is not required (but it doesn't hurt!).
|
||||
|
||||
When executing files without an interpreter, fish, like other shells, tries your system shell, typically /bin/sh. This is needed because some scripts are shipped without a shebang line.
|
||||
When executing files without an interpreter, fish, like other shells, tries your system shell, typically ``/bin/sh``. This is needed because some scripts are shipped without a shebang line.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
|
Loading…
Reference in a new issue