Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site unm-la.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!cornell!uw-beaver!tektronix!decvax!genrad!mit-eddie!godot!harvard!seismo!cmcl2!lanl!dspo!unm-la!cs193aat
From: cs193aat@unm-la.UUCP
Newsgroups: net.micro.6809
Subject: Re: TSedit and OS-9
Message-ID: <249@unm-la.UUCP>
Date: Mon, 4-Feb-85 21:09:40 EST
Article-I.D.: unm-la.249
Posted: Mon Feb  4 21:09:40 1985
Date-Received: Fri, 8-Feb-85 01:53:00 EST
References: <1320@t4test.UUCP>
Distribution: net
Organization: Univ. of New Mexico, Los Alamos
Lines: 33

> 
> 	Since I posted my last article I have been wondering
>     about T/Sedit and how to integrate it into the OS-9
>     system disk. 
> 	
	You should be able to copy it to the /CMDS directory on
	your working diskette along with the defaults startup file.
	I think that by removing edit from the disk and renaming
	TSEdit as edit, you should have no problems.  I have tried
	to use TSEdit with FHL OPAK with little success, it seems
	that they conflict with each other.

> 	Does anyone out in net-land know if T/Sedit can 
>     be put on the OS-9 system disk so that when 'edit'
>     is called, T/Sedit would run instead of the line 
>     editor that comes with OS-9 ?
> 
	See above.

> 	Maybe it could be renamed to 'vi'. I would appriciate
>     it any comments on this subject. Thanks in advance.
> 
	TSEdit can be named vi if you wish.

> 					Joe Roberts

> 					(Intel Corp.)
> 
> 					(t4test@joe)

*** REPLACE THIS LINE WITH YOUR MESSAGE ***
-- 
{{ Mike Mitchell @ UNM Los Alamos }}