Configuration files

[paolo.bormida]

Sorry to bother the forum with this issue, but I find it highly annoying.

After 08.2 release the wiki has been updated to specify how to run Code::Blocks in portable mode, but the entry specifies portability cannot be guaranteed for plugins where C::B is not the maintainer.

After having tried the instructions I have to admit C::B works fine from an usb key, but it always creates two files under %APPDATA%\codeblocks:

  cbKeyBinder10.ini
  codesnippets.ini

Since those plugins are distributed with C::B I would expect them to behave properly and not being rogue with their configuration files.

I might disable them, but if I can do without Code Snippets, KeyBinder is essential to using C::B!

Why doesn't the Key Binder plugin behave more properly?

Paolo

[Pecan]

If you copy the .ini files to your portable CodeBlocks directory just as you copied the .conf files, they'll work the same.

[paolo.bormida]

It seems to work, by copying the ini files in the root C::B folder, but the codeblock folder under %APPDATA% is created empty as well...

Not so elegant but works.

Thanx

Paolo

[MortenMacFly]

Since those plugins are distributed with C::B I would expect them to behave properly and not being rogue with their configuration files.

The core plugins (that are selected by default) just work as expected. If you select to install one of the contrib plugins that there is no guarantee anymore. We cannot do anything about it as contrib plugins are contributed (and surely welcome) but we cannot and will not modify them to follow another strategy the developer had in mind.

Anyways... All the contrib plugins I use just work as expected when following the portable rules for their config files. But that's just because their devs are smart so we all are lucky... so far. ;-)