I have been working on an option to only show the detected compilers in the compiler drop down list. I have finished the initial development and done the first pass of testing this afternoon (OZ time). I will be pushing the changes to the following github branch once I do more testing in a few days, which I hope will eventually be the solution for ticket 1111. See attached PNG for example of the result of the list change (there are also changes for the add/copy/delete/rename for index changes).
https://github.com/acotty/codeblocks_sf/tree/AC-CompilerDialogDetectedOptionTomorrow I will also be pushing a similar change to the auto detected dialog to the following branch, which I hope will eventually be the solution for ticket 1117.
https://github.com/acotty/codeblocks_sf/tree/AC-AutoDetectCompilerStartupTomorrow I will also be pushing my latest compiler XML file to the following branch, which I hope will eventually be the solution for ticket 374.
https://github.com/acotty/codeblocks_sf/tree/AC-AdditionalWindowsCompilerDefsThese changes should help you out allot as the list is way way to big to be usable IMHO and it is worse for newbies.
Okay the order is decided by the weighting in the compiler XML file if you read the WIKI, but I have not spotted this in the code yet. Watch out as I got errors when I deleted some of the compiler XML files before I made the changes as they were getting in the way like you have seen.
Can you add the remove issue to ticket 1111. The force majeur I do is to "rmdir /q /s %APPDATA%\CodeBlocks" BUT BUT it will remove you debugger settings and global variables, but will fix the compiler quirks yo cause when testing new compiler XML and then stuff up the compiler settings. The another option, which may be better is to delete the <compiler><sets> in the %APPDATA%\CodeBlocks\default.conf file and see how CB reacts as this is where the compiler info is stored.
Let me know if you want the AC-CompilerDialogDetectedOption as they are and I will push them up tomorrow.
Let me know how you get on.