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
System: NetBSD 4.99.52 NetBSD 4.99.52 (GENERIC) #0: Mon Feb 
4 13:19:18 CET 2008 i386
Architecture: i386
Machine: i386
        Shell builtins of the C Shell exist as their own manpages -- at least 
        the name of the builtin to the C shell manpage. I can understand the 
        and cultural background of BSD and csh, yet still we do ship with 
        shells, among them two bourne shells (sh, ksh).

        It's confusing to users of the latter shells (and actually I'm writing 
        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 

        Given that on a multi-user system there's no easy way to map virtual 
        for all the builtins of the current running shell into the manpage of 
        very shell, I suggest to simply remove the list of linked manpages, or 
        them by a comment like (e.g. alias):

        "Alias is a shell builtin. SEE ALSO: csh(1), sh(1), ksh(1)" .. or the 

         $ find . -inum $(stat -f %i csh.1)

         $ man alias ;# --> see manpage of csh

        - remove links on csh.1
        - maybe replace by stub manpages as sketched out above


Home | Main Index | Thread Index | Old Index