Unfortunately, -undo_keep defaults to 100. The first thing I do with any new JOE installation is create and modify my ~/.joerc to set -undo_keep to 0, which means "no limit". It's probably overdue to make this the default.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There's a comment in the code saying that the undo_keep variable needs to be a multiple of 2 because of the redo mechanism. I don't quite understand why, but maybe that means it's really more like 50. And once you've undone something, if you do something else, the first thing you did, the undo, and now the new thing are all consuming entries in the log. That's what allows you to walk back over the entire tree and not lose things you undid. Works great if it doesn't throw anything away, as with undo_keep set to 0. I know from experience that the default is very frustrating.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately, -undo_keep defaults to 100. The first thing I do with any new JOE installation is create and modify my ~/.joerc to set -undo_keep to 0, which means "no limit". It's probably overdue to make this the default.
Whatever is that value, the number of resulting undo steps can sometimes be much smaller. Thanks Charles.
There's a comment in the code saying that the undo_keep variable needs to be a multiple of 2 because of the redo mechanism. I don't quite understand why, but maybe that means it's really more like 50. And once you've undone something, if you do something else, the first thing you did, the undo, and now the new thing are all consuming entries in the log. That's what allows you to walk back over the entire tree and not lose things you undid. Works great if it doesn't throw anything away, as with undo_keep set to 0. I know from experience that the default is very frustrating.
See also [#299]
Related
Bugs: #299