Code::Blocks Forums

User forums => Help => Topic started by: DarkHorizon on November 18, 2006, 02:31:45 pm

Title: C::B configuration corruption
Post by: DarkHorizon on November 18, 2006, 02:31:45 pm

Hi all,

Occasionally, for whatever reason, when I attempt to start C::B (Linux), I'll get notification that the application is already started (though nothing appears in ps aux | grep codeblocks). After a reboot, the application launches but with default configuration, as though my IDE configuration has been erased.

I'm not sure why this is happening, and there's a good chance it's something b0rked on my own PC, so I'm wondering if there are certain files in ~/.codeblocks I can back up and then later restore to retain my configuration (dev file paths, color scheme, etc) to avoid having to reconfigure everything in the event it occurs again.

Best regards,
- DH

Title: Re: C::B configuration corruption
Post by: MortenMacFly on November 18, 2006, 02:40:42 pm

Quote from: DarkHorizon on November 18, 2006, 02:31:45 pm

if there are certain files I can back up [...]

Sure, under Linux they should be in $HOME/.codeblocks. For your config, backup all *.conf and *.ini (if there are such). BTW: You can use cb_share_config to transfer the most important settings to another PC/configuration file.
With regards, Morten.

Title: Re: C::B configuration corruption
Post by: DarkHorizon on November 18, 2006, 02:57:37 pm

Thanks! I will try this.