From: Hans-Bernhard B. <br...@ph...> - 2004-04-14 01:35:43
|
On Tue, 13 Apr 2004, Daniel J Sebald wrote: > Rather than doing a full install, I built the latest tarball and decided > to just test it within the "src" subdirectory. I realize "you're not > supposed to do that", but I ran across something a bit strange with the > "gnuplot_x11" terminal. That's exactly the reason you're not supposed to do that. It's explained in the INSTALL file (under "How to test gnuplot"), too. > A couple things. First, it might be nice if gnuplot would check the > current active directory, i.e., the directory from which gnuplot is > launched if it can't find gnuplot_x11 in the expected place. No way. The security guys would immediately hang us by the toes for such a thing. They're nervous enough about the setuid install if the libvga terminal is compiled in as it is. > If nobody likes that idea, fine. However, the second thing is that > after running gnuplot without "gnuplot_x11" present, the command line > hung. Which one: the gnuplot prompt or the shell, after you returned from gnuplot? > CNTRL-C broke from the hang, Broke to where? > but afterward typing any keyboard keys no longer produces a response at > the command line. Which command line? Did you try to clean up the terminal's state typing "stty sane" blindly? > That may be a bug. Could be. Ethan, I guess this one's in your ballbark --- I'm almost willing to bet it's caused by the mouse or font feedback stuff, so please see if you can do something about it. I seriously got to get some sleep now. -- Hans-Bernhard Broeker (br...@ph...) Even if all the snow were burnt, ashes would remain. |