On Fri, Jan 11, 2008 at 05:53:57PM +0100, Paul de Weerd wrote: > | > | right now csh's makefile lists some (not all) builtins as links to > | csh(1). i'm not sure that i see any sense in having MLINKS to builtins, > | to be honest. > > I agree with that but I would add that, as a newbie unix user many > moons ago, I was surprised to not find a manual page for some > "commands" I could run which turned out to be documented in the > manpage of my shell. If 'man jobs' shows me the manpage for a shell > different from mine, I'll take that as a hint to look up the "command" > in the manpage of my own shell. >
yeah, that's a fair point. though to be honest, we already have a good number of ksh builtins with no man page. and whatever shell we go for, we leave users of the other shell at a disadvantage. i think the issue is that having MLINKs for a particular shell is not the correct fix. a better solution, as i see it, is to encourage users to read the man page for the shell they're using, and to use commands such as "whence" to find out what exactly they're executing, and man/locate to find stuff. perhaps afterboot(8) or help(1) could hint at this. jmc
