From: Fred Holmes 
@Date: Wed, 22 Jan 2003 14:52:31 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au



Carlo Hogeveen's "UndoJump" macro is "good enough"
without spending time on 
it.  For the moment, anyway.  But I would prefer a straight
"undo" for each 
and every movement of the cursor to a new position.  Carlo's macro only 
undoes (stores on the stack) "large" jumps, with the macro code defining 
what is "large."  So I sometimes can't undo a jump that I've made because 
it wasn't large enough to be recorded on the stack.

I though of mentioning this earlier, but then didn't.  Carlo has work to 
do, but every time I make a remark about one of his macros he rewrites it 
immediately, and makes me feel guilty for not working on it harder 
myself.  I could probably figure it out, after studying Carlo's code, but 
it hasn't yet percolated to the top of my priority list.

The use I'm making of it is to go back to the source of a block move or 
copy, after the move/copy has been made and after I've done some minor 
editing at the destination, such as fixing the white space before and after 
the block (having not been careful about whether the block includes leading 
and trailing blank lines).

If the cursor position is stored as an offset from the beginning of the 
file, then the restored position may not be the "real" previous position, 
if the intervening keystrokes have added characters to the file.  This 
comment is based on something I think I saw somewhere, not on actual 
observation of performance.  Or the stack values could be "adjusted" based 
on the insertion of characters earlier in the file?

I haven't looked at the Projects macro.  I've never looked at it, but 
understand from discussion here that it's a fairly comprehensive macro for 
managing large projects with multiple files.  I would want to look into the 
code for that which is a undo function for cursor repositioning, and move 
that out into a separate, independent macro.  Something that also hasn't 
moved to the top of the priority list.

Thanks,

Fred Holmes

At 02:34 PM 1/22/2003, Sammy Mitchell wrote:

>Fred Holmes wrote:
> >Has anyone worked up a macro so that one can move the
> >cursor back to several iterations of "previous position,"
> >i.e., routinely keep a stack of definable depth of the
> >cursor position and retrace with successive keystrokes of
> >the same keystroke combination.
>
>Just curious, did any of the suggested solutions give you
>what you were wanting?
>
>--
>Sammy Mitchell
>
>--
>TSEPro mailing list

--
TSEPro mailing list



---
[sawasdi.apana.org.au] (3:800/846.13)