Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rochester!jpayne
From: jpayne@rochester.ARPA (Jonathan Payne)
Newsgroups: comp.emacs
Subject: Re: interactive shell in jove
Message-ID: <25604@rochester.ARPA>
Date: Fri, 6-Mar-87 11:50:59 EST
Article-I.D.: rocheste.25604
Posted: Fri Mar  6 11:50:59 1987
Date-Received: Sun, 8-Mar-87 06:16:30 EST
References: <632@cadre.dsl.PITTSBURGH.EDU>
Organization: U of Rochester, CS Dept., Rochester, NY
Lines: 28
Keywords: emacs jove versions



The version of JOVE that was sent over mod.sources was supposedly the
latest and greatest.  If JOVE did pty's in the version that comes with
4.3, it should work fine in the later versions.  What doesn't work about
it?

Since I sent JOVE to mod.sources I've gotten several bug fixes (10 times
over ...) and a few enhancements.  I've fixed everything and incorporated
most of the enhancements.  Often I've tried to reply to the people sending
the fixes, but the mail bounced.  So if you're wondering why I never reply
that's probably why...

I'm also wondering how to make interactive processes work better on
versions of UNIX that don't have the SELECT system call.  What's THE
right way to do things?  The way I did it once was to have EVERYTHING
come in over a single pipe, including input from the keyboard.  There were
initially two processes, JOVE and the kbd process.  The kbd process read
characters and passed them on to JOVE with a little header identifying
it.  Subshells just used the same fildes, so JOVE was sitting there
reading one fd ... it just worked.  Main problem was that it was too slow
for keyboard input.  v7/2.9BSD pipes were implemented with disk files.  It
would probably work well with systems with sockets, since they use incore
buffers.  But those systems also have SELECT, which is the best way,
anyway.  So what's the right thing to do?

Anyway, this is my path.  jpayne@rochester.arpa, or jpayne@cs.rochester.edu
or something like that.  I think rochester talks to seismo via uucp ...