CodeLite IDE

I am having an issue where codelite will not remember my workspace settings, and won't open then on relaunching the IDE.

The basics:
version: 12.0.0, downloaded from Codelite website for Ubuntu bionic (12.0-1 unofficial.bionic).
Os is Linux Mint 19.0 XFCE

One oddity to note is that I could not load plugins for this version, Synaptic says that it depends on codelite (=10.0+dfsg-2) which is an older version.

Any advise?

Hi,

One oddity to note is that I could not load plugins for this version, Synaptic says that it depends on codelite (=10.0+dfsg-2) which is an older version

Synaptic is correct .
The official debian (etc) codelite is split into 2 packages: the plugins and the actual IDE. The version of both is still 10.0. You installed the unofficial 12.0 codelite package which contains both the IDE and its plugins; look in the Plugins menu and you'll see those.

I am having an issue where codelite will not remember my workspace settings, and won't open then on relaunching the IDE.

That's strange. Where is the workspace meant to be saved? Is it actually there? Any confounding factors e.g. a different filesystem?
And what about CodeLite's settings; your preferred theme/font etc? Are they remembered?

Regards,

David

There is a *.workspace file, and it knows what projects are in the workspace, but that's it. It does not keep track of which files were open or where in the file I was. The most recent workspace does not load on the next boot, even though "Load last session on startup" is selected. Theme and fonts are remembered. No unusual file systems are involved, a standard Linux Mint install, although in a VirtualBox, but that shouldn't matter. Weird.

in a VirtualBox, but that shouldn't matter.

Indeed. I use VirtualBox extensively without this sort of trouble.

The most recent workspace does not load on the next boot, even though "Load last session on startup" is selected.

There should be a file called sessions.xml. It's probably in ~/.codelite/config/ or ~/.codelite-dbg/config/ or similar. That should contain the addresses of the LastActiveWorkspace and LastSession. Does it for you?

There is a *.workspace file ... It does not keep track of which files were open or where in the file I was.

No, it shouldn't.
If your 'Foobar' workspace path is /path/to/Foobar/, you should have a file /path/to/Foobar/.codelite/Foobar.session which holds those values. Does it exist? Does it change when you alter something (e.g. the active editor) and then close the workspace?

Are any of those filepaths readonly? Do you (meaning the CodeLite instance) have r/w permissions for them? Do their modification times change when you close the workspace?
Do any of the paths contain symlinks? Do any span filesystems? (Yes, I'm scraping the bottom of the barrel now.)

What happens if you create a new workspace and add one of the template projects, accepting the default filepaths? Does that then behave itself?

The permissions for the workspace .codelite folder is 775, and within that folder my .session file (0 bytes, btw, and the date is when the workspace was created) is 664. the *.tags (only owner has write permission) and *.workspace.* (same persmissions as session file) files have a creation date of today.

No symlinks or spanning file systems.

OK. And did you try creating a new workspace/project?

Yes, I just created a simple hello world workspace and test project in a completely different folder. Same results, except now there is no *.session file whatsoever. I have another linux virtual machine in which codelite is running perfectly, although it is version 10 on Linux Mint 17, and the new machine is running version 12 on Linux Mint 19. Now difference whatsoever in file permissions.

Very strange. I just tested the bionic CL 12.0 in a Mint 19.0 (Mate) VBox guest. It behaved normally.

One last suggestion: close CL, then temporarily rename your ~/.codelite (or whatever it's called). Restart CL, run the startup wizard, then create a new workspace/project again. If that behaves, your original ~/.codelite must in some way be corrupt.

If there's still a problem, I've run out of ideas.

You could try installing Mint 19.1 instead... .

Hey, that did it! The only issue I had was the IDE did not remember the configuration of my cross compilers. I just cut and paste the proper section from the old .codelite/config/build_settings.xml file into the new version, and all my projects compile properly, and codelite is remembering all my workspace settings just like it should.

Thanks alot, that was a great help!