Date: Wed, 17 Jul 2002 20:48:40 +0200 From: Sheldon Hearn <sheldonh@starjuice.net> To: Garrett Wollman <wollman@lcs.mit.edu> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/man/man1 builtin.1 Message-ID: <20020717184840.GB751@starjuice.net> In-Reply-To: <200207171734.g6HHYdRi097476@khavrinen.lcs.mit.edu> References: <200207170712.g6H7CcIv098084@freefall.freebsd.org> <200207171734.g6HHYdRi097476@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On (2002/07/17 13:34), Garrett Wollman wrote: > I would like to see separate manual pages for each of these (in the > style of the POSIX spec), but I don't care to do the work myself, so > anyone is welcome to have at it. I'd also like to see builtin(1) make > a clearer distinction between reserved words (like if, while, for, do, > done, and fi) and things that are actual commands. The description in > builtin(1) of the external commands (called ``regular built-in > commands'' in POSIX) should probably point out that almost all of them > are useless and included only for standards compliance. How do you feel about the suggestion of implementing all these external commands that only serve to satisfy a POSIX brainfart as wrappers that say "um, your shell script might actually work if you don't provide the full path to me"? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020717184840.GB751>