Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

According to this URL I should be able to start Komodo IDE from the command line when I want to edit a file.

I set up the symbolic link using (on single line)

ln -sf "/Applications/Komodo" 

but when I type

afg-2:~ lexu$ komodo .bash_profile

I get

dyld: Library not loaded: /usr/lib/libsqlite3.dylib Referenced from: /System/Library/Frameworks/Security.framework/Versions/A/Security Reason: Incompatible library version: Security requires version 9.0.0 or later, but libsqlite3.dylib provides version 1.0.0 /Applications/Komodo line 131: 4370 Trace/BPT trap
"$prog" ${1+"$@"}

and a dialog that says:

komodo-bin cannot be opened because of a problem

My guess is I need to somehow let Komodo know it needs to use different libraries?

Does someone have this working?

share|improve this question
up vote 3 down vote accepted

Add alias ki='/Applications/Komodo\' to your ~/.bashrc

Then just do $ ki somefile

EDIT: Changed it, didn't realize you were using Komodo IDE

share|improve this answer
I'd tried that before, but got a different error that lead me to believe starting the '-bin' was a nono! (I'll add that as an Edit to the Question though!) – lexu Apr 12 '10 at 14:41
OOPS: I just realized you are going the alias route .. that worked! Problem solved! – lexu Apr 12 '10 at 14:47

Does it work if you call the program directly from it's regular location? If so, then very likely there is a dependency on where the program is located. To get around that you could, instead of having a symbolic link in ~/bin/komodo, make that file a small script such as:

exec /Applications/Komodo

Change the permissions of that file with "chmod 755 ~/bin/komodo". Then it should work (assuming the problem was that it worked OK from its original location).

You could also adjust your PATH variable to include /Applications/Komodo . Then there would be no need to have a symbolic link or script in your ~/bin .

share|improve this answer
Nope, didn't work, I get the same error when using exec – lexu Apr 12 '10 at 14:42
exec /Applications/Komodo\ did work however! Thanks for teaching me about exec! – lexu Apr 12 '10 at 14:51

The way I do it is have ~/bin/ which has

/Applications/Komodo\ "$@"

I then have ~/bin as part of my path

I can then do

$komodo index.php

and it loads. However because I like to be even quicker, I have a shell alias which is:

alias kom="komodo"

so that I can do:

$kom index.php
share|improve this answer

the exec solution kind of worked for me but when closing the Komodo window/app it closed my iTerm (with all of it's tabs :-(

For an OSX'ian approach:

open /Applications/Komodo\

If you associated files with komodo you can call open from the command line. e.g. if you right click on a .py file and click on get-info, say open-with komodo and click on Change-All, you can then from the command line just say:


share|improve this answer

That FAQ is out of date. We'll make sure that gets updated. The best way to start komodo from the command line on OS X is to use 'alias' like so:

alias komodo='open -a "Komodo IDE"'


alias komodo='open -a "Komodo Edit"'
share|improve this answer
Thanks for the replay, please edit your reply and add a path to the new FAQs, when available. – lexu Jan 10 '11 at 7:15
Should you be disclosing an interest? The faq here require "you must disclose your affiliation in your answers". – pnuts Dec 2 '12 at 22:26

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .