wohler@SPAM.ISTC.SRI.COM (Bill Wohler) (03/20/87)
okay, wierd bug alert.
i had a clock, xterm console window, and gnuemacs window. then, i
ran makeit in my console window, hit ^Z to stop the thing and then
gnuemacs died and the window disappeared and i noticed that both uwm
and xclock were stopped (the console window was the same as their
controlling tty, ttyp0). (later, i was able to get the same
behavior with make, but it only did it about 5% of the time as
opposed to 100% of the time with makeit).
playing some more, i found that if i interrupted makeit with ^C
while it was running (in the console window, mind you), "Quit" would
appear in the minibuffer of my gnuemacs window! i wasn't able to
get the same behaviour with other programs. i don't know why i
haven't observed this before but i haven't been compiling much until
now since i brought up 3.2 (see below) and usually run makeit in the
background right away.
bringing the x server down and then back up did not clear the
problem.
has anyone else observed this? or is this a harbinger of a coming
natural disaster? all i know is that it was damned annoying.
[hmmm, just tried using the csh rather than tcsh and cannot repeat
the problem. another tcsh bug, great... nevertheless, the
behaviour of the tcsh in the console window affecting the emacs is
odd.]
here are the details:
machine: sun 2/50 running sun-os 3.2
gnuemacs: "GNU Emacs 18.36.6 of Wed Jan 28 1987 on c3-5 (berkeley-unix)"
x: 12/24/86 X10R4 release
xterm: 6.6A2
uwm: whatever comes with the R4
makeit: 'echo "" >>! Makelog;' \
'echo `date` `who am i | ' \
'awk '"'{print "\$"1}'"'` >> Makelog;' \
'echo % make \!* >> Makelog; make \!* >>& Makelog'
shell:/usr/local/tcsh
coffee: pete's espresso, grinder setting 5.
--bw
ps. anyone know just who is maintaining tcsh these days? paul
placeway at ohio state was a couple of years ago, but he hasn't
replied to my recent letters. i have some bug fixes and am looking
for more from people...gwu@vlsi.cs.cmu.edu.UUCP (03/23/87)
It sounds like tcsh isn't setting up process groups correctly. Rather than explaining something over the network when you can just look it up, take a look at the manual entry tty(4). George