I searched for it in the C::B dir.
Big ow!
You should not have a config file inside the Code::Blocks directory, unless you did that on purpose and you know what you are doing. Things like that can lead to a lot of confusion.
To explain further, under Windows, the application searches for a configuration file with the currently active profile's name (not necessarily default.conf) in the following locations:
- the configuration folder (
C:\Windows\AppData\codeblocks or something similar)
- the data folder (
CodeBlocksDir/share/codeblocks- the folder containing the Code::Blocks executable
- the currently active user's "My Files" directory
If no profile was specified, then default.conf will be used. If a profile was specified but not found, it will be created. If no profile was specified and no default profile is found, it is created.
The reasoning behind this is to allow both user-specific profiles as well as pre-configured installations on read-only media such as CD-ROMs. As you can see, the settings stored in the executable folder will
not be honoured if you have settings stored in the configuration folder (which will be the case if you have run Code::Blocks before). Thus, it may happen that you search in one file and make modifications, but strangely you never see any effect!
Therefore, best keep the files where Code::Blocks puts them, unless you really *need* to do it differently.
Under Linux, different locations are used, but similar rules apply.