Komodo

How Do I Install New Dictionaries for Spell-Checking

Question: 

How do I install a new dictionary for Komodo's spell-checker, such as British English or German.

Answer: 

Komodo uses Mozilla's dictionaries. Each dictionary consists of two files, ln-LC.aff and ln-LC.dic, where "ln" is the language's two-letter ISO language code, and "LC" denotes its two-letter locale code. Komodo ships with the files en-US.aff and en-US.dic in the <komodo-install-dir>/lib/mozilla/dictionaries.

You can either copy existing Mozilla dictionaries from other programs, such as the <thunderbird-install-dir>/dictionaries directory, or find the dictionary you need at http://www.mozilla.com/en-US/thunderbird/dictionaries.html

Download the .xpi into a temporary directory, unzip it, and copy the .aff and .dic files to <komodo-install-dir>/lib/mozilla/dictionaries

Komodo should offer the new dictionaries in the Check Spelling dialog's Language drop-down bar. There is no preference to change dictionaries -- Komodo assumes that the most recent language is your preferred one, and remembers it.

One thing to keep in mind is that these dictionaries install into the program's installed area, not the profile area. This is a known bug with all Mozilla-based programs, and work is in progress to improve this on an overall basis -- the new spell-checkers will reportedly be faster, support more natural languages, and will be installed into the profile area. For now, when you migrate from version 4.2 of Komodo to a newer version, you'll have to manually copy the dictionaries over (unless the Komodo installer does that for you at that point).

Komodo column selection

Question: 

Does Komodo support column (block) selection?

Answer: 

Yes, to perform a column selection in Komodo, you will need to hold down the Shift and Alt keys whilst performing selection movements. For large blocks, it is often easier to select the area with the mouse first using the default selection method, then change the selection to a block selection by holding down the Alt and Shift modifiers and using the arrow keys to refine.

What about column editing?

No, column editing is not support by Komodo. Column editing is a follow-on from column selection, in which as you edit, changes are made to all the lines in the block selection, not just the current line.

How to improve Komodo's editing performance

Question: 

In what ways can I increase the performance of the Komodo application?

Answer: 

There are numerous components inside of Komodo that can become a performance hindrance, especially on older computing machines. Luckily, there are a number of features and components that can be turned off. Here are a few of these most common performance sensitive components that can be disabled:

  • Code Intelligence autocomplete and calltips (fires from editor key press events)
  • Syntax checking, aka linting (fires after code changes)
  • Disable wordwrap, as this can become intensive for files with long lines
  • Disable folding, this intensifies the code parsing process
  • Ensure there are no mixed line endings (will show up as green squiggles)
  • If using Komodo IDE SCC integration, ensure the "Do recursive status checks" preference is turned off

Startup ideas

  • Reduce the number of opened files and projects? As this is a large contributor to the startup speed.

Platform specific ideas

  • Mac OS X: Ensure you are using the correct build for your Mac architecture, check the "Komodo->About" menu, it should be macosx-x86 if you have an Intel machine, else macosx-powerpc for PowerPC. See here on how to check your system: http://support.apple.com/kb/HT1531

Feel free to add others as you come across them.

Cheers,
Todd

Problems with Ubuntu Gutsy Tribe releases

Question: 

I've just installed Komodo 4.1/4.2 on Ubuntu 'Gutsy' 7.10. When I click edit (in the main menu) - preferences, the preference dialog box appears but hangs.

Answer: 

This seems to be an issue with pre-release builds of Ubuntu Gutsy when using a GTK theme other than 'Human'. There seems to be a problem with 'inhuman' themes currently that prevents Komodo and Firefox from working correctly. Switching back to the 'Human' theme fixes the issue.

Access violation errors in PHP 5 / Komodo 4.1.1

Question: 

PHP crashes when debugging PHP5 code with an access violation warning on Windows when debugging with Komodo 4.1.1. Is there a workaround for this?

Answer: 

There seems to be a bug in the php_xdebug.dll file included for PHP 5.2.3 and possibly other versions. The workaround is to use a newer build of php_xdebug.dll from pecl4win:

http://pecl4win.php.net/download.php/ext/5_2/5.2.1/php_xdebug.dll

Why doesn't Rails debugging work on Windows?

Question: 

I was following the Rails tutorial, and everything was working like a champ until I got to the debugging part. The cmd window fires and sits there doing nothing. I understand Rails is all about a zen approach to building web apps, but isn't more supposed to happen?

Answer: 

Yes, the debugger should kick in. The problem is that shortly after the Rails tools were developed, Ruby 1.8.6 was released, and the Windows version of 1.8.6 fixed a bug. The bug was that the Dir#[] class method was accepting paths containing backslashes and quietly converting them to forward slashes, even though the documentation stated that the first argument is a regular expression. While Rubies 1.8.5 and earlier could have an expression like "Dir['c:\\foo\\bar\\*.rb'] and find all the Ruby libraries there, version 1.8.6 (and up I suppose) quietly returns an empty list.

The problem is that the Komodo debugger is extensible, and loads all its modules at run-time, by running Dir[] on a path based on its location. On Windows this path happens to contain backslashes. It didn't used to be a problem. It's fixed on the beta 4.2 versions of Komodo, but if you're trying to get the debugger to run on 4.1, you'll need to make this fix:

Find the file /lib/support/dbgp/rubylib/rdbgp/command.rb
load it in Komodo (or any other editor), find the load_dbgp_commands method,
and add the second line (the 'dir.gsub!' one):

def load_dbgp_commands
  dir = File.dirname(__FILE__)
  dir.gsub!(/\\/, '/') if RUBY_PLATFORM["-mswin"] # Allow for 64-bit, i686
  Dir[File.join(dir, 'commands', '*.rb')].each do |file|
    require file
  end
end

Komodo Documentation in PDF format

Question: 

Is the Komodo User Guide available in PDF format?

Answer: 

Yes. A PDF version of the documentation for Komodo IDE 6.1.2 is available here.

Please feel free to give your feedback on the appearance, usability and general usefulness of this format.

How to prevent freeze-ups on dual-core Windows machines

Question: 

I run Komodo on a dual-core Windows machine. Occasionally after running a Perl program, either inside the debugger or outside, Komodo will freeze up. This seems to happen whether the CPU is Athlon or Pentium, it doesn't seem to matter.

Answer: 

The key is to open the task manager, select the komodo.exe process, right-click
it using the "set affinity" function.

Remove the checkmark from all but one CPU and komodo will work fine.

Thanks to community contributor JTa for working this out.

You can track this bug at
http://bugs.activestate.com/show_bug.cgi?id=53927

Mini-faq: how to debug Expect with Tcl

Question: 

While trying to debug an expect program, I get tracebacks referencing functions that start with "DbgNub". What should I do?

Answer: 

Usually this problem can be resolved by running the program with the
tclsh interpreter, not expect, and ensuring the code contains this
line:

package require Expect

PHP configuration fails on Windows Vista x64

Question: 

I am using a Windows Vista x64 system, and get an error when trying to configure PHP for debugging. Is there are fix for this?

Answer: 

This problem is because Komodo is installed to the path

C:\Program Files (x86)\

on Windows Vista x64, and php.ini will not allow paths with parnthese characters in it. There are two possible workarounds:

1. Run the debugger configuration wizard and specify that Komodo's php.ini and php_xdebug.dll should both be placed on a safe path, preferably something like:

C:\php5.2\xdebug\

2. optionally reinstall Komodo to C:\Program Files\ instead.