[Coder] Feature request: prevent closing a Coder with unsaved method edits

[khinsen]

I lost a lot of time today due to closing Coders by accident in which I had started to edit methods, but not saved them.

There are three problems that contribute to this:

1. As long as there is a syntax error in a method, I cannot save it.
2. All Coder tabs say "Coder", so if you have several open Coders you end up switching by trial and error.
3. Switching to a tab and closing the tab differ only by a few pixels on the screen.

So what happened is that, while working on an unfinished and unsaveable method, I looked at other classes to find the right methods to call, and ended up closing my Coder in the process, by accidentally clicking on its close button.

[girba]

Thank you.

[seandenigris]

Just dreaming but if we had a univeral undo mechanism, the holy grail would be to record a "discard edits" command instead of popping up "are you sure?!" dialogs like Pharo. Maybe a first step would be to keep a buffer of a few recently closed tabs...