I blew it with disown again

[Dan Jacobson]

# emacs /usr/share/doc/junkbuster/&
[2] 1338
# disown
bash: warning: deleting stopped job 1 with process group 1207

As Homer Simpson would say, "doh" I stubbed my toe.  Pilot
error. The old "forgot about the old stopped job number one routine"
as Maxwell Smart would say.

OK, I remember that I can still do
# kill -CONT 1207
# $ 
# $ 
Oh great, now I have two shells reading from the same terminal.
You see, my job [1] was "su news".
[Now what does one do to separate the Siamese twins now?]  

Anyways, pray tell, why is there no child guard cap on "disown" for
average bumblers like me?  How about a warning before the disaster
instead of after, unless set -o something or non interactive.

Let's report the bash version via "env":
# $ e
bash: e: command not found
# sh: n: command not found
$ v
bash: v: command not found
never mind. 2.05a.
-- 
http://jidanni.org/ Taiwan(04)25854780