NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
misc/37981: shell builtin manpages are for csh(1) only...
>Number: 37981
>Category: misc
>Synopsis: shell builtin manpages are for csh(1) only...
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: misc-bug-people
>State: open
>Class: doc-bug
>Submitter-Id: net
>Arrival-Date: Fri Feb 08 12:50:00 +0000 2008
>Originator: Martin S. Weber
>Release: NetBSD 4.99.52
>Organization:
>Environment:
System: NetBSD circe.entropie.net 4.99.52 NetBSD 4.99.52 (GENERIC) #0: Mon Feb
4 13:19:18 CET 2008
root%circe.entropie.net@localhost:/src/obj/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
>Description:
Shell builtins of the C Shell exist as their own manpages -- at least
linking
the name of the builtin to the C shell manpage. I can understand the
historical
and cultural background of BSD and csh, yet still we do ship with
alternative
shells, among them two bourne shells (sh, ksh).
It's confusing to users of the latter shells (and actually I'm writing
this
after being asked by a user) to see shell builtins valid for their own
shell (in this case "alias" for a ksh user) map into manpages of a
foreign
shell.
Given that on a multi-user system there's no easy way to map virtual
manpages
for all the builtins of the current running shell into the manpage of
this
very shell, I suggest to simply remove the list of linked manpages, or
replace
them by a comment like (e.g. alias):
"Alias is a shell builtin. SEE ALSO: csh(1), sh(1), ksh(1)" .. or the
like.
>How-To-Repeat:
$ find . -inum $(stat -f %i csh.1)
./bg.1
./limit.1
./csh.1
./alias.1
./dirs.1
./fg.1
./foreach.1
./history.1
./jobs.1
./popd.1
./pushd.1
./rehash.1
./repeat.1
./suspend.1
./stop.1
./source.1
$ man alias ;# --> see manpage of csh
>Fix:
- remove links on csh.1
- maybe replace by stub manpages as sketched out above
>Unformatted:
Home |
Main Index |
Thread Index |
Old Index