Describe the solution you'd like
It would be nice if omm(1) could give the user a chance to edit the context if it exceeds the limit to avoid losing work.
Is your feature request related to a problem? Please describe.
omm(1) has a limit on the number of bytes in a context. If this limit is exceeded, the context is thrown away when the editor exits and whatever was there is lost. This came up in discussion of issue #56.
Describe alternatives you've considered
If the above is not possible, then omm(1) could not delete the tmpfile after the editor exits to allow the user to recover the text.
Additional context
The main thing I would like is for work to not be lost. It's frustrating and causes the user to lose trust in the stability of the software.
I had a long, structured checklist as the context for one task. I reached a stopping point and saved and didn't think to check that the save was successful. When I went back to the task I was very confused by the task context not being there any more.
FWIW, I tend to subscribe to the "0, 1, or infinity" rule, https://en.wikipedia.org/wiki/Zero_one_infinity_rule, within the practical limits of the operating environment, of course. There are plenty of reasons to disagree and I'm not trying to impose any philosophies, just throwing it out there in case you haven't heard of it before.
Describe the solution you'd like
It would be nice if
omm(1)could give the user a chance to edit the context if it exceeds the limit to avoid losing work.Is your feature request related to a problem? Please describe.
omm(1)has a limit on the number of bytes in a context. If this limit is exceeded, the context is thrown away when the editor exits and whatever was there is lost. This came up in discussion of issue #56.Describe alternatives you've considered
If the above is not possible, then
omm(1)could not delete the tmpfile after the editor exits to allow the user to recover the text.Additional context
The main thing I would like is for work to not be lost. It's frustrating and causes the user to lose trust in the stability of the software.
I had a long, structured checklist as the context for one task. I reached a stopping point and saved and didn't think to check that the save was successful. When I went back to the task I was very confused by the task context not being there any more.
FWIW, I tend to subscribe to the "0, 1, or infinity" rule, https://en.wikipedia.org/wiki/Zero_one_infinity_rule, within the practical limits of the operating environment, of course. There are plenty of reasons to disagree and I'm not trying to impose any philosophies, just throwing it out there in case you haven't heard of it before.