Komodo profile structure

Posted by toddw on 2008-01-29 10:57
OS: All / Any | Product: Komodo | tags: profile
Question: 

Can you explain what each item in the Komodo profile directory relate to?

Answer: 

Komodo profile location
To find the location of the Komodo profile directory (also known as the Komodo application data directory), please see this faq:
http://community.activestate.com/faq/komodo-file-locations#appdata_dir

Directory structure

8.0/
prefs.xml
Stores all of the user preferences for Komodo. If you
want to reset your Komodo preferences, the easiest way
is to simply remove these two files and Komodo will
rebuild them with the default values on next startup.

prefs.xmlc
A "pickled" cache copy of prefs.xml. It is re-generated if
removed.

doc-state.xmlc
This file stores the individual file preferences, set
through the "Edit->Current File Settings" menu. Things
like the current file position, indentation settings,
encoding, bookmarks, folding and eol settings.

view-state.xmlc
This file stores view state, such as the MRU (most
recently used) ordering, recently opened files, tab
ordering position, etc...

toolbox.sqlite
Stores information about your Komodo toolbox. You can copy
these between profiles, or to another machine.

tools/
Contains JSON files for each of the tools in your toolbox.

apicatalogs/
All API catalogs (codeintel cix files) that are added through
Komodo's "Code Intelligence" preferences get copied to this
directory.

project-templates/
Stores all known project templates, available when
using the "File->New->New Project From Template" menu.

templates/
Stores all known file/language templates, available when
using the "File->New->New File..." menu.

samples/
This is where Komodo stores the sample files and projects.

schemes/
This is where Komodo stores the user's custom keybindings
and color schemes.

autosave/
The Komodo auto-save feature will save information
relating to Komodo's unsaved files in this directory.
If you open a file that has a matching backup in this
directory, Komodo will offer to restore the backup.

codeintel/
Code intelligence information. When Komodo scans any
source code file (PHP, JS, Python, etc...) or API
catalogs, it saves this processed information (containing
the function and variable information, calltips etc...)
to a file in this directory.

If you Komodo code intelligence is not working, it can
often be fixed by shutting down Komodo, removing this
directory and then starting Komodo again, which will
then cause a rescan/recreate of the necessary code files.

XRE/
Details relating to the Mozilla base that Komodo is
using (extensions, dialog and window settings, remote
file encrypted password files, etc...).