ActiveState Community

Not for Windows, but it is possible on a Mac or Linux machine. This does not work on Windows because the Windows Komodo build uses a different locking mechanism, which is a kernel lock specific to the application name and version.

By default Komodo will not allow you to have two instances of Komodo running at once, this is because the Komodo profile directory cannot support multiple instances. You can get around this profile directory limitation by using a separate profile directory for the second instance!

You can use a custom profile directory by simply setting the KOMODO_USERDATADIR environment variable. If you set a different value to this variable for every subsequent komodo session you want to run, then you'll be able to have multiple komodo sessions running.

Example to run two different Komodo sessions on Linux/Mac:

# export KOMODO_USERDATADIR=/home/toddw/.komodoide_session1
# komodo
# export KOMODO_USERDATADIR=/home/toddw/.komodoide_session2
# komodo

Note: You do not need to use a separate KOMODO_USERDATADIR setting for the default (first) instance, it will use the Komodo default setting if not supplied. The default location details are here:
http://community.activestate.com/faq/komodo-file-locations#appdata_dir

Now, the problem with this is that there is no shared information between the two sessions. Your toolbox changes, session state, preferences, code intelligence, etc... will only ever be seen by the same/one Komodo instance, similar to how the Firefox bookmarks, session and preferences are separated between Firefox profiles.

Cheers,
Todd