From xemacs-m  Sun Feb  2 01:56:21 1997
Received: from localhost.interport.net (ts5port44.port.net [207.38.250.44])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id BAA12613
	for <xemacs-beta@xemacs.org>; Sun, 2 Feb 1997 01:56:19 -0600 (CST)
Received: (from pez@localhost) by localhost.interport.net (8.7.4/8.7.3) id CAA04094; Sun, 2 Feb 1997 02:58:23 -0500
Date: Sun, 2 Feb 1997 02:58:23 -0500
Message-Id: <199702020758.CAA04094@localhost.interport.net>
From: Peter Pezaris <pez@dwwc.com>
To: Kyle Jones <kyle_jones@wonderworks.com>
Cc: xemacs-beta@xemacs.org
Subject: Re: Undo!
In-Reply-To: <QQcbcr19912.199702020628@crystal.WonderWorks.COM>
References: <199702010502.AAA03861@localhost.interport.net>
	<kign2tozwpd.fsf@jagor.srce.hr>
	<QQcbcr19912.199702020628@crystal.WonderWorks.COM>
Reply-To: pez@dwwc.com


    Kyle> Can someone explain what a redo is supposed to do?

    Kyle> I like Emacs' undo system, probably because my mind
    Kyle> doesn't have trouble chasing and remembering long chains
    Kyle> of pointers.  The direction reversals and all that seem
    Kyle> imminently logical to me.

You're editing a file.  You go to the beginning of the file and do a
batch of non-trivial editing.  Later, you go to a different part of
the file and do another batch of non-trivial editing.  Then it hits
you; the first batch of editing has a mistake in it that you have to
change.  You hit undo 47 times to get back to that point, and change
the thing that needs to get changed.  Wouldn't it be nice to hit
"redo" 47 times to get back to where you really want to be?

Instead of the current scheme where undos get pushed on the undo
stack, under the undo/redo paradigm undos get popped off the undo
stack and pushed onto the redo stack.  The opposite happens for
redos.

If you've never used an editor with this capability then you'll have
to trust me; it's a much more intuitive and (more importantly) much
more powerful paradigm.

-Pez

