Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!rochester!rit!ultb!jdb9608
From: jdb9608@ultb.isc.rit.edu (J.D. Beutel)
Newsgroups: comp.sys.atari.st
Subject: break
Summary: how are programs interrupted on the ST?
Keywords: RTX job control vi ksh csh SIGSTOP _main cli isr
Message-ID: <3060@ultb.isc.rit.edu>
Date: 5 May 90 02:33:06 GMT
Reply-To: jdb9608@ultb.isc.rit.edu (J.D. Beutel)
Organization: Rochester Institute of Technology, Information Systems
Lines: 28


Does anybody know how break (i.e., ^C) works on the ST?
Is it something in TOS?  (I wouldn't think so since I don't
remember hearing about it, and I know some programs don't break.)
Is it done in each language?  For instance, does _main() in
Sozobon C scan stdin for ^C and _exit() if it sees it?
(I wouldn't think so since then everything would have to
worry about it.)

I'm asking because I'm toying with the idea of a vi-type
Korn shell based on RTX.  I like gu:lam but I don't like microEmacs,
and I miss multi-tasking and job control.  So, thinking about
device drivers, SIGSTOP, and the like, I really should understand ^C.
I suppose I could just have the cli slip in an isr to monitor
whatever tty-type input devices, and grap any ^Z that comes along,
but there'll probably be complications if I don't understand 
what else is going on.

Or, does Dave Beckmyer's (sp?) shell have vi-like command line editing,
and job control?  I haven't seen it, and from what I heard it's a C shell,
but if it does have those other features I'd hate to re-invent the wheel.
I've seen the RTX docs and have the highest respect for RTX's design
(it reminds me of the kernel my OS Lab team did).

-- 
--
J. David Beutel  11011011  jdb9608@cs.rit.edu      "I am, therefore I am."
Looking for co-op Sept..Feb in NN, OS, VR, or AI.