From bca250b0b2a1df4ceb939b71a269f71501fda024 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Thu, 30 Jul 2026 03:21:52 +0000 Subject: Prepare for 2.10.0.0; remove pedantic posix; support loopwhilex -x "" --- doc/cd.html | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) create mode 100644 doc/cd.html (limited to 'doc/cd.html') diff --git a/doc/cd.html b/doc/cd.html new file mode 100644 index 0000000..fbd6687 --- /dev/null +++ b/doc/cd.html @@ -0,0 +1,60 @@ + + + + + + + execline: the cd command + + + + + + +

+execline
+Software
+skarnet.org +

+ +

The `cd` program

+ +

+cd changes the current working directory to a +given directory, then executes a program. +

+ +

Interface

+ +

+     cd dir prog...
+

+ +

+cd performs a +chdir() +system call on dir, then execs into prog.... +

+ +

Notes

+ +

This cd program will never be invoked by a shell, unless its full path +is explicitly given to the shell command line. So it is perfectly acceptable and valid +to have a cd binary in the filesystem. No confusion will be possible: shells +will invoke their builtin +cd +utility, and execline scripts will invoke the cd binary.
Previous versions of POSIX also required a conformant cd binary to exist +in the filesystem, for no reason at all. So, in previous execline versions, +a posix-cd binary was present, and cd could be installed as a symlink +to it when execline was configured with the --enable-pedantic-posix option. +This allowed distributions to make execline binaries, including cd, available +in PATH, while strictly conforming to POSIX. This requirement has now been relaxed by +POSIX, so the needlessly complex posix-cd program was replaced with this +simpler cd, that can now be made available in PATH without breaking strict +conformance.

+ + + -- cgit v1.3.1

The cd program

Interface

Notes

The `cd` program