🚀 go-pugleaf

>2. EMACS: Who can tell me when ^y (yank) in micro-emacs will bring back
>just the last thing deleted (per the emacs convensions) or a whole
>bunch of other deletions which seem to be trying to make up for the
>lack of a kill ring buffer, and is quite annoying. Sometimes, for
>long streches of time, it just (corectly in my opinion) puts just the 
>last thing, and sometimes, the whole kitchen sink gets plopped down
>in the middle of what you are doing, without even setting the mark on
>the other side! (Oh, I guess that was a flame!) Perhaps I'm suffering
>from old version-itus? is it fixed in the latest? (oh please add word wrap!)
>
>
>			Allen King	aking bfly-vax.bbn.com ucbvax

MicroEMACS 3.x keeps a flag indicating what kind of command the last
command was. Whenever you do a kill, if the immediatly previous command
was NOT a kill, then the kill buffer is first cleared, and then the text
is saved. Consecutive kills accumulate in the buffer, and kills after a
cursor move or other command clear the buffer and start over. This is
very predictable and I have had no problem reports on it.

MicroEMACS, from version 3.3 and up ( 3.9 is current) has had WRAP mode.
Just type ^XMwrap<RET> and the word WRAP will appear on the mode line.

If you are using a very early MicroEMACS (Dave Conroy's original
probably) I would suggest updating to something more current.

			Daniel Lawrence		(317) 742-5153
			UUCP:	{ihnp4!pur-ee!}j.cc.purdue.edu!nwd
			ARPA:	nwd@j.cc.purdue.edu
			FIDO:	201/2 The Programmer's Room (317) 742-5533