Custom compiler settings not saved

[MC]

I have setup a custom compiler config (executables, command line options, output parsing, commands) from settings..compiler settings and eventually
using advanced compiler options. I use codeblocks 13.12 on windows 7 and windows 8.

I recognized that these settings do not hold when quitting and restarting codeblocks again sometimes.
For example i set up the CC65 compiler tool chain by adding a new compiler and it seems that these quite permanently persist.
On the other hand i added assert failed and test failed output parsing options to gcc and they do not survive quitting and restarting of codeblocks.
Can i somehow manually request the settings to be saved? Or can you say under which circumstances settings persist and under which not?
I urgent need some reproducible procedure to make these compiler settings permanently.

Thank you !

[scarphin]

I'm not sure if it will work but there is a 'save everything' menu item.

[BlueHazzard]

i think there was a bug about this not saving....
can you try a nightly build?

greetings

[stahta01]

When I have this issue or related, I open Code::Blocks (CB) with no projects open and do this.

1. disable all the plugins not needed except for the compiler plugin
2. shut down and restart CB
3. make the changes needed
4. shut down and restart CB
5. verify the changes were saved
6. Enable any plugin I normally use.
7. shut down and restart CB

The problem happens for me because CB has an error on shutdown and fails to save changes because of the error.
The above steps always avoided the shutdown error for me.
Often, just NOT opening a project or workspace was enough to avoid the error on shutdown.
The CB plugin I suspected most often was the Code Completion (CC) plugin.

Tim S.