Bad trap (Re: Questions about rewriting the History function.)

[Blair P. Houghton]

In article <32120001 at hpfcdc.HP.COM> pbm at hpfcdc.HP.COM (Peter McLain) writes:
>  You can get asynch job notification in ksh88 by doing:
>
>	trap "jobs -n" CHLD

Which reminds me; why, in sh(1), does

	trap 'echo foo' 18

(where signal 18 is SIGTSTP) give a '18: bad trap' message?
The manual page (Ultrix 3.1) says that SIGCONT, SIGSTOP,
and SIGKILL are the only untrappable signals.

Dang it!  I _want_ to do some massaging on a ^Z!

				--Blair
				  "Gadzooks!  I _asked_ one... :-/"