i think time-based might be awkward because if you don't type for a while, your first several (potentially many) strokes of the undo command would have no effect. maybe a certain number of keystrokes? whatever aquamacs does works fine by me, so i would mimic if possible. On Monday, December 12, 2005, at 01:50AM, Martin Renner <[EMAIL PROTECTED]> wrote:
>>On Dec 8, 2005, at 5:21 AM, Parlamis Franklin wrote: >> >>> since this topic is pretty popular, let me mention a problem i have >>> found with the integrated editor from R.app: >>> >>> the "undo typing" command seems to remove an arbitrary number of >>> keystrokes. at times, i will make a mistake, then when i go to undo >>> it, i find the editor has undone not only my mistake but a >>> significant amount of prior work. >> >>The problem is to decide when to put in a checkpoint. Right now, we >>are forcing them only after <Enter> which is ok for usual work, but >>if you are only fixing a line here or there then those won't be >>checked in. Should we use some time-based limit? Cocoa's default is >>to place no checkpoints so it's not a help :P >Since you mentioned christmas - ideal might be a short time limit (10 >s?) and multiple undos. Knowing how the checkpoint is set already >helps a great deal. > >Cheers, > Martin > >_______________________________________________ >R-SIG-Mac mailing list >R-SIG-Mac@stat.math.ethz.ch >https://stat.ethz.ch/mailman/listinfo/r-sig-mac > > _______________________________________________ R-SIG-Mac mailing list R-SIG-Mac@stat.math.ethz.ch https://stat.ethz.ch/mailman/listinfo/r-sig-mac