weil@dataio.UUCP (Steve Weil) (08/15/85)
I have an application which needs to run an editor script with ex (sed
and ed will not do). Even though my environment is properly set with
TERM and TERMCAP, when I type "ex < file", the editor does not seem to
know my terminal type. On the VAX (4.2) this is not so bad, but on an
NCR Tower ex refused to do any editing without a cursor addressable
terminal. Depending upon specifics, I got messages like:
Terminal must have UP capability to use open/visual mode
(even thought the only command in the file was "set"), or
Unknown terminal type "dumb"
Is anyone familiar with this problem? Is there a workaround?
By the way, does the Tower have a Unisoft port?
Thanks in advance,
Steve Weil Data I/O
dual!unisoft!dataio!weil entropy!dataio!weil
ucbvax!lbl-unix!uw-beaver!teltone!dataio!weilpeter@baylor.UUCP (Peter da Silva) (08/19/85)
> Terminal must have UP capability to use open/visual mode > (even thought the only command in the file was "set"), or > Unknown terminal type "dumb" Try execing 'ex' with argv[0]='edit'. Then it won't try to do a 'set open'. Of course that shouldn't be a problem, because I've used 'ex' on dumb terminals before... -- Peter (Made in Australia) da Silva UUCP: ...!shell!neuro1!{hyd-ptd,baylor,datafac}!peter MCI: PDASILVA; CIS: 70216,1076
ccrdave@ucdavis.UUCP (Lord Kahless) (08/23/85)
> > Terminal must have UP capability to use open/visual mode > > (even thought the only command in the file was "set"), or > > Unknown terminal type "dumb" > I only saw the reply. Are you trying to redefine standard input to ex? % ex <script won't work but % cat script |ex will work perfectly. ucbvax!ucdavis!vega!ccrdave