Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!decvax!decwrl!labrea!rocky!stergios
From: stergios@rocky.STANFORD.EDU (Stergios Marinopoul)
Newsgroups: comp.sys.amiga
Subject: Bug in MicroEmacs V1.1 (?)
Message-ID: <264@rocky.STANFORD.EDU>
Date: Thu, 23-Apr-87 07:31:08 EST
Article-I.D.: rocky.264
Posted: Thu Apr 23 07:31:08 1987
Date-Received: Sat, 25-Apr-87 09:39:26 EST
Reply-To: stergios@rocky.stanford.edu (Stergios Marinopoul)
Distribution: world
Organization: Stanford University Computer Science Department
Lines: 46


I have found a bug in MicroEmacs V1.1 that was released in the Enhancer.

Heres what you need to do to reproduce it:

	emacs filename

	before doing any editing split the screen.

	select a new buffer for the top window, say temp.

	go back to the bottom window and set a mark (remember no editing 
		has been done so the cursor is at the top left of the bottom 
		window) and copy a region of any length (for this example 
		use two lines.)

	kill and yank it back.

	go to the top window and yank the selection there too.

	what, you say you can't see it?  Neither can I!  Do another yank,
		and another.

	Save the file in the top window; the file in the temp buffer,
		to newfile.

	Quit emacs.

	Run emacs newfile.

	Tada!  There are 3 copys of the region you cut from the origonal
		file.

The lines I copied where two #include statements if it matters.

Can anyone else verify this please?  This is the first problem I have ever
encountered using microemacs, and at that, no biggie.  Just thought I'd
pass it along.

Stergios Marinopoulos
S&M Engineering

-- 
% UUCP:         !decwrl!rocky.stanford.edu!stergios			%
% ARPA:		f.flex@othello.stanford.edu				%
% USnail:	Crothers Memorial #690, Stanford, CA. 94305		%
% Pa Bell:	(415) 326-9051						%