Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!batcomputer!itsgw!steinmetz!uunet!ubvax!ardent!rap
From: rap@ardent.UUCP (Rob Peck)
Newsgroups: comp.sys.amiga
Subject: Re: WorkBench 1.3
Summary: watch out...
Message-ID: <652@ardent.UUCP>
Date: 18 Oct 88 23:06:03 GMT
References: <362@laic.UUCP>
Organization: Dana Computer, Inc., Sunnyvale, CA
Lines: 39

In article <362@laic.UUCP>, darin@laic.UUCP (Darin Johnson) writes:
> Comments on 1.3:
>   [other comments deleted]
> 
>   The MicroEmacs on the Extras disk is lots better than V1.2
>   (mouse support), although not as great as I would like.


One of the nice improvments in this version is that brace, bracket
and parentheses matching is implemented for programming in C.  Also,
clicking the mouse in a non-current buffer window sets that buffer to
be the current one (equivalent of emacs command ^Xp or ^Xn to that
buffer's window.)

BUT... watch out while editing.  MEmacs supports "set-mark" by double-
clicking on a single position, or effectively by single clicking on
the actual cursor.  The released version has a bug (it has been reported)
and CBM has checked it out... supposed to be fixed soon and fix to be
posted to BIX... the problem is:

	The ACTUAL marked position is at least two lines
	higher than the position at which you double-clicked.
	It may occasionally be unpredictable exactly where the
	mark actually is if the double-click is used (sometimes
	found it 2-5 lines higher than I expected).

This can get really difficult if one moves regions around a lot
and relies on setting the mark using this method.

So this is not a BIG deal if one is aware that it happens so you just
quit using this one feature.  Forewarned is forearmed.  So just watch
out for this until the update becomes available.

I am very pleased with the other improvements, including the ability
to execute commands from a named file, effectively allowing an unlimited
number of customized macros to be created out of the existing commands.
So check it out, if you will.  Just watch out for this now known bug.

Rob Peck