What to do when ocean input gets stuck?

[Svenn Are Bjerkem]

Hi,
when doing some typing on the ocean command line, I got into something
that I obviously don't get out of. I get no feedback just new linefeeds,
and ctrl-c give me back the prompt with an error message
*Error* parser: interrupted while reading input.
I can't use ctrl-z to background it to kill it.

Is there some magic way to end the command line input parsing, or do I
have to kill the window and start a new one?
--
Svenn

 

[Andrew Beckett]

On Wed, 12 Jan 2005 10:43:51 +0100, Svenn Are Bjerkem <svenn.are@bjerkem.de>
wrote:

Hi,
when doing some typing on the ocean command line, I got into something
that I obviously don't get out of. I get no feedback just new linefeeds,
and ctrl-c give me back the prompt with an error message
*Error* parser: interrupted while reading input.
I can't use ctrl-z to background it to kill it.

Is there some magic way to end the command line input parsing, or do I
have to kill the window and start a new one?

I've seen this happen with the ocean executable sometimes. Unfortunately
because of the way that the interface is implemented, this kind of thing
happens. Also it annoys me that trace output is swallowed in the ocean
executable...

I think it's a consequence of how the GUI is replaced by a textual input,
whilst still keeping the GUI behind the scenes.

Probably should log a service request for it, although I'm sure it's hard to
reproduce...

Andrew.