> If somebody (not necessarily me) was to put interrupt functionality > into rc, you could basically experience 70s UNIX again--assuming you > are happy using ed. I'd try putting in the interrupt thing, but I > expect it would require removing the functionality from rio, which I > don't care to do :)
"interrupt functionality" in rio is very simple. when rio is processing keyboard input (which it must do anyway, to multiplex the keyboard among the many windows), if it sees a DEL, it writes "interrupt" to /proc/pid/notepg, where pid is the pid of the original rc process that rio kicked off for that window. it doesn't make sense to put this into rc or take it out of rio, because rc doesn't process keyboard input (especially when it is waiting for a subshell to complete), and rio must, for multiplexing. if you want to be able to use DEL to stop programs without running rio, the right way to do that is to write a little input processing shim that opens /dev/cons in raw mode and then presents a new /dev/cons, /dev/consctl as a file server and kicks off a subshell. mostly it just makes input from the original /dev/cons available on the new one, but when it sees a DEL in non-raw mode, it writes "interrupt" to the notepg file. this little file server would be independent of the shell or program running. i doubt it would be very long. russ
