It cant be helped, but i cannot press enter more than three times without pressing CTRL+S in between...
Finally someone who at least knows the problem, even if you don't seem to see it that way. How would you describe that behaviour? Pressing CTRL-S every few seconds? Manic? Compulsive?
Thing is, I've noticed exactly that behaviour on myself. It is sick - and completely unnecessary. Ergo: a problem.
(as a sidenote: during writing this reply, I had to step away from the keyboard, to do something else. I did not bother to save the draft somewhere outside the web-formular, because there is no chance in hell, that the browser crashes while I'm away, just because an edit window is open.)
I've read your whole post, but I guess you're not reading or understanding mine.
I've asked you some questions. I'm out of the conversation unless you answer those.
I have answered every single question of you. I've answered them before you asked them, but still...
I've said that the crashes you see aren't that rare, because you're loosing your recent work too often, so it becomes a problem that bothers you so much that you'll start a topic on the forum. Am I correct in my understanding of the problem?
FYI - I started looking for alternatives right after the first crash. And to be clear about that: the crashes are not the problem, the possible loss of work is.
And yes, I still am able to use CB and get my work done, obviously. But how is that the question? What bothers me, is that I'm becoming a nervous CTRL-S-monkey. You have no idea, how often I had to delete signature lines from the git-gui commit message window - because CTRL-S does not "save" there but "sign". But again: this was already stated in the middle of my first post.
How often do you see crashes? Once a day? Once a minute? More often?
As I described in the first post: sometimes none for months, sometimes several a day. The crashes are random. Always in the editor but not always during editing - sometimes just while moving the cursor.
It seems that you want one thing only and if you don't get it you won't cooperate in any other way.
Quite the contrary. I keep getting told, how my problem is not a problem but normal behaviour. How that declaration of bankruptcy called autosave is the only possible solution.
Well, you are right in one way: I won't stick around to help you fix random crashes that don't occur sometimes for months. That would be futile. I told you, which part of the code I'm suspecting and I gave you a feasible workaround.
Auto-save plugin will save only modified files, not all open files.
And in your eyes, this makes all the difference, because who would be so crazy and not always have every file saved after every modification, right? Who would be so crazy, when one always has to fear, that the editor crashes and loses your work.
Dude, you /really/ need to take a step back and look at the whole situation here
You have an immutable "that's the way it is and has always been and has to be for all eternity" stamped in your brain. That is a pity, because most probably you are not even half my age - and it's the old folks who are supposed to be stuck in their ways. Well, maybe thinking that a crash should not always lose you your work is old fashioned. Historically, it's the opposite: old crappy OS like DOS just terminated your program in case of crashes, and therefore autosave /was/ the only solution (short of "not crashing", ofc). But now, on modern unix-based desktops, your program gets told, when it does something crash-worthy, and you get a chance to do some cleanup before you accept the crash. signal() is your friend
I've now altered autosave to think in seconds instead of minutes, because the chances of this thread leading to something productive are zero, and that's all of a "solution" you're willing to consider.
Thanks for trying to talk me out of my problem. But you're no jedi, and i'm still quite aware of which droids I'm looking for