I have trouble interrupting a running octave program with Ctrl-C.
Sometimes it works, mostly it doesn't (especially for "heavy" programs).
Undoubtedly octave "sees" the Ctrl-C, because a "line-feed" occurs, i.e.
the screen moves up a line leaving a blank line below; but the program
Am I right in guessing that this failure to stop the program on Ctrl-C
occurs if the program is in an inner loop, or evaluating a function call,
i.e. not at its "top level" when Ctrl-C is pressed?
(octave is running on Linux; this behaviour is independent of kernel
It would be very nice if things could be arranged so that Ctrl-C would
stop the program in fairly short order: I quite often want to quit out of
a trial run giving unwanted results, when left to itself the program will
run for another 20 minutes or more (on a Pentium-120!)