From: Gerben Vos <gpvos@gpvos.org>
To: dash@vger.kernel.org
Subject: doc omission: . searches path
Date: Sun, 20 Oct 2024 22:27:51 +0200 [thread overview]
Message-ID: <359236b66220f58cdee2b59a1991c25b@gpvos.org> (raw)
Hi all,
a small omission in the man page: it says: ". file: The commands in the
specified file are read and executed by the shell."
However, dash only takes the specified file if it contains a '/'; if
not, it searches $PATH for it (and errors if it is not found, even if
the file exists in the current directory). The behaviour is fine, but
this should be mentioned in the man page. The process is like the points
1 and 2 under "Path Search" (but without checks for functions and
builtins of course).
Cheers,
Gerben Vos.
reply other threads:[~2024-10-20 20:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=359236b66220f58cdee2b59a1991c25b@gpvos.org \
--to=gpvos@gpvos.org \
--cc=dash@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox