Hi, ropers wrote on Sun, Jun 23, 2019 at 05:35:06PM +0200:
> This is made slightly clearer by the language used in the POSIX spec > and on a bunch of other, non-OpenBSD man pages derived from it: In general, we don't like the style POSIX describes things all that much. It may be the adequate level of formalism required in a specification, but many aspects feel overly technical for a manual, and then all those "shall" and "must" which feel unfriendly in a manual page... >>> The cd utility shall change the working directory of the current >>> shell execution environment... > http://pubs.opengroup.org/onlinepubs/9699919799.2013edition/utilities/cd.html > If that's all correct, then would it make sense to retrofit any of the > above enlightening language (from 8.4 or POSIX) into OpenBSD's sh or > ksh man pages? I don't suppose a separate cd(1) man page makes sense? > (There's cd(4), but that's different.) No, we don't write separate manual pages for shell builtins. It was discussed internally whether the chdir(2), getcwd(3), pwd(1), and ksh(1) manual pages can be improved to make it more explicit that the current working directory is a process property. But the conclusion was that introducing wording to that effect risks causing other ambiguities, while the fact that the cwd is a property of each process is actually fairly obvious in the first place. What else could it possibly be, in a multi-user system? So the manual pages remain unchanged. Yours, Ingo
