ActiveState Community

Komodo 4 and Interpreter Paths - what happened?

Posted by bryanrieger on 2007-02-03 13:50
OS: Windows XP Pro

I had been using the Komodo 4 Beta without issue for PHP and Ruby dev and just purchased an upgrade last night. Upon installing it I'm finding things that worked in the beta no longer work.

Ruby Interpreter
Ruby is on my PATH but Komodo can't find it. Opening a Ruby interactive shell in Komodo produces a dialog stating 'There was an unexpected error starting the debugger'. Setting the language preferences for ruby - ie specifying the interpreter does nothing - it's always blank upon opening the dialog again. That said, opening a Windows command prompt and typing ruby -help does infact fire up the ruby interpreter.

PHP Interpreter
PHP is on my PATH (and this option is set in the 'Use this interpreter' drop down.
Re-check config does nothing, and the Debugger Config Wizard get's to the second screen, displays the PHP installations found 'c:\Development\PHP\php.exe' (the the 'php-cgi.exe'). In attempting to setup the above installation and clicking next - the wizard simply does nothing.

The only thing that does anything in the wizard is 'back' (duh) and cancel - which prompts 'Are you sure you want to cancel installing the PHP debugger support'.

This is INSANELY frustrating!!!
What happened - this stuff worked just a week ago?
I'm scared to actually start using this thing now as I'm really unsure what else is broken.

Windows XP SP2
Komodo IDE, version 4.0.1, build 274919, platform win32-x86.
Built on Mon Jan 29 12:48:03 2007.

FYI - I've reparied, uninstalled, reinstalled, deleted prefs, application folders, etc. a number of times and nothing seems to change. I'm also getting the exact same error with the Python interpreter.

Sincerely,

Bryan Rieger

COMSPEC problem
shanec | Mon, 2007-02-05 14:22

The issue was due to a COMPSEC variable problem. Details are:

[Trent wrote to Bryan]
> What is the output of running the following commands in your shell?
>
> set COMSPEC
>
> dir c:\development\python

[Bryan Rieger wrote]
> C:\>set COMSPEC
> ComSpec=C:\WINDOWS\system32\cmd.exe;

[Trent wrote]
> Aha! I think that is the problem. That semi-colon at the end will kill
> any command that tries to run via the shell -- as Komodo does with
> the debugger, etc. invocations.

Bryan Rieger wrote:
> FANTASTIC!!! Removing the ';' in the COMSPEC setting did it.
> I would never have suspected that.