I think some part of the blame lies with the software, and in particular with an undo command whose use is often misleadingand confusing.I agree. The most obvious sense of "undo" in which users want an undo command is so that they can undo their previous command, not so that they can undo the previous step NB took to fulfil their previous command. One way of solving the issue would be to have a "stepwise undo" command which behaves as NB's undo currently behaves, *and* a straightforward undo command which retraces all the steps taken by NB since the user issued their last command. If you've not sent your tale of woe to NB-NY, I think you should.
This illustrates one of the problems in designing software to please everyone, because I personally prefer "undo" the way it is and would have a problem with a change. The reason is that I understand the various F11 combinations to invoke a macro (an XPL program which invokes a series of commands in sequence) rather than a command. If "undo" undid every command in an XPL program before stopping it could do some serious damage.
Bob Kelly -- Robert A. Kelly Professor of Systematic Theology, Assistant Dean - Academic Waterloo Lutheran Seminary Wilfrid Laurier University 75 University Ave. W. Waterloo, Ontario N2L 3C5 Canada 519-884-0710, ext. 3853 Fax: 519-725-2434 rkelly@wlu.ca http://www.seminary.wlu.ca/rak/