This is a question to the designers and in a sense
can only be answered by the thinking
behind the design.
In editors I know, there are two main alternatives,
undo the last change and "get me out of this mess",
otherwise known as exit without saving.
For what you want to be possible, -doedit- must understand
a "set" of changes, or "one go", in the way you do.
What is your definition that can be rendered programmable?
Yet another alternative: you are showing, in effect,
a wish for a more flexible editor. Recommendations
a-plenty can be found in
http://fmwww.bc.edu/repec/bocode/t/textEditors.html
In my own favourite editor, for example, I can
go backwards and forwards in a set of changes
at whim.
Nick
[email protected]
Nishant Dass
> Does anyone why Stata only undoes the very last change you
> have made in the do-file editor as opposed to the last
> "set" of changes (all done in one go)?
>
> Since Stata is smart, I understand there must be a very
> good reason for it but I am just curious why, because it
> would be very convenient if it were the other way around -
> i.e., being able to undo a whole set of commands that are
> done in one go.
*
* For searches and help try:
* http://www.stata.com/support/faqs/res/findit.html
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
