Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/3/84; site garfield.UUCP
Path: utzoo!utcsrgv!garfield!wolf
From: wolf@garfield.UUCP (Wolfgang Thomeier)
Newsgroups: net.micro.6809
Subject: Re: Miserable OS-9 editor
Message-ID: <1709@garfield.UUCP>
Date: Tue, 30-Oct-84 13:11:30 EST
Article-I.D.: garfield.1709
Posted: Tue Oct 30 13:11:30 1984
Date-Received: Tue, 30-Oct-84 22:44:45 EST
References: <698@ihuxa.UUCP>
Organization: Memorial U. of Nfld. C.S. Dept., St. John's
Lines: 73

[Munch, munch, gobble, gobble, yum, YUM!!!]

I am posting this at the request of a friend.

Start of forwarded article:
---------------------------
> Re: response to some of those questions on the OS9 EDITor.
>
> > Did I get a bad copy of the editor (EDIT) with OS-9 for the Color 
> > Computer, or is the thing totally brain-damaged?  The worst problem
> > I have with mine is that if an existing file is read in on the
> > command line, the file is SHUFFLED!
> > ... 
> > 					Dan Hoelker
> > 					ihnp4!ihuxa!mstach
>
>	Your editor copy of the os9 editor is fine.  OS9 wouldn't load it
>	if it was faulty; however, your problem arises from the brain-damaged
>	:-] manner in which one is expected to use the editor.
>
>	Your problem is that doing a 'R*' in the editor loads the content
>	of the file and places it where you are in the buffer--when just
>	entering a file you are at the top, so 'R*' puts the rest of the file
>	at the beginning of the buffer.
>
>	Solution:
>
>1.	When calling the editor use a memory specification which exceeds the
>	actual file size by at least 2K.
>
>	i.e.	EDIT file #8K
>
>	to edit a file that is about 6K or less.
>	this causes the editor to load in the whole file, eliminating the
>	chance of scrambling your file.
>
>2.	anoter way around this is to read in the rest of the file at the end
>	of the current buffer.
>
>	i.e.	"/R*"	when entering the editor (note the "/")
>
>	this will read in the rest of the file and append it to the end of
>	the edit buffer.
>
>NOTE:	It is a good idea to get into the habit of *always* doing a "/R*"
>	immediately when entering the editor, so that you will always be
>	sure of having the whole file in memory.
>	(it is not necessayry to do a `READ""` before doing a "/R*" because
>	this is default when entering the editor.
>
>	The same guidelines are true for the 'w' command.  You *must* place
>	yourself at the top of the buffer to write from there.
>
>	i.e.	"^w*"	will write the whole buffer in the correct order.
>
>	don't forget to close the file you are writing to by doing a
>	` write"" ` after the 'w*'.
>
>	Someone posted a question on how to quit the editor without updating
>	the file -- here is how.
>
>		".shell"
>		OS9:"procs"
>		OS9:"kill n" where n represents the ID# of the EDIT process.
>		OS9:"DEL scratch" (to clean up after the editor).
>
>	*ONLY* enter the commands enclosed in the "" please!
>
> Hope this helps
-------------------------------------------------------------------
{akgua, allegra, ihnp4, philabs, princeton, utcsrgv}!garfield!caveh
------------------------
End of forwarded article