ActiveState Community

I started off to evaluate Komodo today, however it appears that there are some issues with it not working properly unless ruby is in the path that it expects? I've seen mention of this floating around the web with no solution. The evidence is that it appears that the config checks out via "Check Configuration," however when I try create a "New Project From Template..." it just returns without actual running the rails command and generating the project files, etc.

Please advise as I only have (had really) a limited time to evaluate Komodo and this really has marked a very bad start.

I'm trying to create a Rails project from a template but when I do, I get an error saying "Ruby installation at /usr/bin, but rails isn't installed there." This is correct, however I have rails installed some where else and do not want to install it in /usr/bin. I can issue "rails -v" from the terminal fine so it's not an issue of it not being available. How can I tell Komodo where rails is actually installed?

Prior to upgrading form 4.0 to 4.1 I was using the SVN integration and quite happy with the results. However, since the upgrade, my SVN status icon on any open file always displays a check mark in a green circle indicating that my file is in sync with the repository. I have tried modifying files outside of Komodo and have had the same result. Since Komodo is never aware that my files are out of sync, I cannot update or check in.
Is anyone else experiencing a similar problem with SVN?

When using Komodo Edit in Mac OS X, the close and maximize buttons are usually disabled. Sometimes they are enabled, but most of the time they are grayed out. Does anyone know how to get them to work all the time?

4.1 Beta2 on OS X. I have a network share mounted on my desktop, and a few files opened on that share. If I choose the "open file" dialog from within Komodo Edit and try to use the directory browser drop down to go up a level in the directory tree, I get a crash. Reliably happens, every time. I've attached the crash report. Can anyone else duplicate?

So, Textmate has two extremely useful keyboard shortcuts, meta-t and shift-meta-t. Those open a dialog where you can incremental search against all the functions in the current document. It seems to even remember which one you used last, from all the matches. The next is same but for all files in the project. What are the best equivalents in Komodo?

I see that you can find all functions into the results window but not sure how to do an incremental search (ideal) on those results.

Despite some warnings in Komodo docs, I was running Eaccelerator and Xbedug extension at same time. I just thought I was lucky and could enjoy both. Well, the debugger was broken in subtle ways. Namely, it would skip ahead various lines when i *step into* a function. Step over worked fine, Step in didn't. So if you are having PHP debugger weirdness like that, disable the Eaccelerator and use APC or XCache. Both of those are compatible, in my testing.

I have Perl Deployment Kit 6 on Windows XP, and am using it very successfully. I now need to deploy to OS X without worrying about which CPAN modules are present. The Active State website seems to imply that upgrading to 7.0 would allow me to build OSX packages, is that true for just the deployment kit, when running on Windows? I don't want to find out the hard way that I have to buy the full IDE or run a separate product on a Mac.

OS X 10.4.9, Komodo 4.1b2.

When I use the new option to "Run to First Breakpoint" it seems that Komodo does not properly close the debugging connection. When I try to disable debugging in Firefox using XDebug Helper, sometimes nothing happens when I click on the icon (i.e. it won't turn off). If I quit Komodo and restart I get an error message:

Unable to initialize the debugging system because the debugger could not bind on port 9999... Debugger Initialization Error.

I'm at my wit's end trying to enable readline support for ActivePython 2.5.0 in OSX. For past versions, it was simply a matter of compiling readline and moving the readline.so file to the appropriate python directory. For 2.5.0, this no longer works. My freshly-compiled version is not even recognized -- no error messages in the console, nothing -- and moving the file from my 2.4.3 installation results in all sorts of warnings.