ActiveState Community

Komodo started from the command line wierdness

Posted by Pev on 2008-10-02 08:45

Sorry if this has been posted before, I searched the forum and bug db but didn't find anything obviously similar.

If I start Komodo from within a shell (Console cmd/msys bash/ipython pysh) then the language checking and auto-completion don't work.

e.g.
> komodo.exe hello_world.py

If I hover the mouse of the the script error on the status bar (!) I get the following error message

Unexpected internal error checking 'hello_world.py' with activestate.com/koLinter?la...

This happens whether I start komodo in it's install directory e.g.
[c:\Program Files\ActiveState Komodo Edit 4]
> komodo.exe c:\mystuff\hello_world.py

or if I start it where the file is e.g.
[c:\mystuff]
c:\Program Files\ActiveState Komodo Edit 4\komodo.exe hello_world.py

If I start komodo from the desktop shortcut or start menu and then open the file with the open file dialogue then the language checking and auto-completion works.

If I start Komodo from the desktop shortcut or start menu and then open a file from the command line e.g. the Komodo Edit application is already running and I type...

> komodo hello_world.py

...at the command line, then that also works!

When I run Komodo in verbose mode the problem goes away, perversely. However, the following log message can be seen...

ERROR: root: unable to connect, status 403.

Other stuff from the verbose mode logs:
komodo: debug: Komodo information:
komodo: debug: Version: Komodo Edit 4.4.1 (Build 1774)
komodo: debug: OS type: Windows XP
komodo: debug: Komodo startup options:
komodo: debug: nFiles: 1
komodo: debug: file 0: hello_world.py

toddw | Thu, 2008-10-02 10:24

Thanks for the report. This looks like the following Komodo bug:
http://bugs.activestate.com/show_bug.cgi?id=76208

For a workaround, you might want to try running Komodo from a Windows Command Prompt, and supply the verbose "-v" command line argument:

"C:\Program Files\ActiveState Komodo Edit 4\komodo" -v

Cheers,
Todd