From e20d78431bfe897762ba7194455fa57c26ea08ed Mon Sep 17 00:00:00 2001 From: David Adam Date: Tue, 21 Feb 2023 21:12:53 +0800 Subject: [PATCH] docs/index: update some formatting from #9482 --- doc_src/index.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc_src/index.rst b/doc_src/index.rst index a7bbf0058..70043e79c 100644 --- a/doc_src/index.rst +++ b/doc_src/index.rst @@ -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 =============