Xref: utzoo comp.bugs.misc:115 comp.bugs.sys5:434
Path: utzoo!mnetor!uunet!vsi!friedl
From: friedl@vsi.UUCP (Stephen J. Friedl)
Newsgroups: comp.bugs.misc,comp.bugs.sys5
Subject: Re: Problem with JOVE editor
Message-ID: <619@vsi.UUCP>
Date: 27 Apr 88 02:43:01 GMT
References: <307@pyuxf.UUCP>
Organization: V-Systems, Inc. -- Santa Ana, CA
Lines: 25
Keywords: No such device
Summary: your ksh ENV file

In article <307@pyuxf.UUCP>, daveb@pyuxf.UUCP (david berk) writes:
> I have a strange problem using the JOVE editor on a Vax running
> System V.  When I run a shell command via C-X ! the shell command
> executes fine in a window, however "stty: No such device" precedes
> the output.  This only occurs when my shell is defined as korn
> shell.

Disclaimer: I've never used JOVE but I'll give this a shot.

When JOVE runs your command, it almost certainly communicates with
it via pipe so it can put the output into a window.
When ksh starts up, it looks for the $ENV environment variable,
and if it is found, it executes all the commands found in the
file so specified (much like .profile).  What is probably happening
is that your $ENV file (say, ".kshrc") contains a stty command.

Stty does an ioctl(2) on stdin, and the "no such device"
means that this file descriptor is not a character device;
a pipe will give this message.  Move the stty command from
the $ENV file to your .profile and the error will go away
and will probably make everything you do run a little faster.

-- 
Steve Friedl           V-Systems, Inc.        Spaf for president!
friedl@vsi.com   {backbones}!vsi.com!friedl    attmail!vsi!friedl