My personal viewpoint is that the final release candidate should be the same as the released version. For example, OpenOffice 2.0RC3 and OpenOffice 2.0 Final have
the same md5sum. Firefox 1.5RC3 is identical to Firefox 1.5 Final, although I haven't checked the md5sums there.
Anyway, we could go to an RC4, but we might go straight to final. When we do go to final, this project is going to get a lot of publicity (hello Slashdot), and people from other editors are going to check it out. I think it would be amazing if the first time it's run, a dialog pops up asking what editor they are used to, and sets up the initial keystroke bindings to match what they are familiar with. I've used ConTEXT and Visual Studio extensively and can list all the key bindings for each one. Of course, the default option on that dialog would be "Use Code::Blocks default keys." Other people here can fill in for other popular "normal" editors. Obviously we can't use VIM keys since they aren't regular bindings. But there's UltraEdit, Eclipse, JEdit... others I'm sure. We don't have to get all just ones that people here are already familiar with. Shouldn't take long to set up a couple different default profiles.
Can we do this before RC3 so it's tested and ready for our slashdot users?