ActiveState Community

Just got around to installing Komodo on my Fedora 9 laptop. There's apparently something I have to tell SELinux to let it work:

[znmeb@DreamTimeF Komodo-IDE-4.3.2-17463-linux-libcpp6-x86]$ ./install.sh
Enter directory in which to install Komodo. Leave blank and
press 'Enter' to use the default [~/Komodo-IDE-4].
Install directory:

install: Installing ActiveState Komodo to '/home/znmeb/Komodo-IDE-4'...
relocate this Python to '/home/znmeb/Komodo-IDE-4/lib/python'
relocate '/home/znmeb/Komodo-IDE-4/lib/python/bin/python2.5-config'

I've found snippets of clues in a number of places but no direct answers to the following:

Telnet session has been 'spawned' within Expect to a remote host. The remote host terminal control (vt100 or ansi) is using line-wrap when various commands are used. My particular issue is when I 'send' a command like 'cat filename' and the file has lines in it that are longer than the current term column setting for the spawned telnet session.

I'd like to disable line wrap and then restore it after issuing my 'cat' commands.

Hello folks,

I am really new to tcl and linux, so running a tcl/tk program in Fedore is not easy to me. Here is the problem: when i try to run the tcl file, it reports that it "can't find package math".

I installed tcl and tk in /usr/local/bin: I can find tclsh8.5 and wish8.5 under this directory.(I may not complete moving the lib file part when i installed it, i am not sure).

Hi,

I have been looking at a problem one ouf our customers was having using ActivePerl to connect via DBD:ODBC to our SQL Server driver on Linux. After investigating, the problem seems to be that the version of iODBC you have built your distribution with expects the W (wide) functions (SQLDriverConnectW, SQLConnectW) to use four byte unicode. Unfortunatly that will fail with just about every ODBC driver out there that exports the W functions, as most of those will expect 2 byte wide characters, just the same as on Windows

Most of the time when komodo crahsed I am not able to restart komodo, hence I always remove host- directory located in komodo application data directory. This resulted in some of the preference/setting being reset to default the next time I start komodo. What is the proper way to clean-up and restart komodo after a crash.

I recently installed Komodo IDE 4.2.1 on Red Hat Linux. I'd like to upgrade to 4.3.

1. I'm unable to use the "Check for updates" option. It eventually times out. I originally had this same problem on my Windows installation of Komodo until I properly configure Komodo's proxy settings. I've now done this on my Linux installation, but I still get "AUS: Connection timed out". When I select "Open Komodo Community" Komodo launches Firefox and I'm connected. Firefox and Komodo have identical proxy settings. Any help on this?

There is something weird happening since the 4.3 KomodoEdit upgrade, on CentOS 5.1 with Gnome interface.
Just to make sure, I deleted everything related to old version, including the .komodo directories for all users (floren and root).
The install went OK. After the init process, I left everything default, except the font size.
Now, if I fire KomodoEdit as root user, I cannot replace in files one word at the time. However, the Replace All works fine. More details:

Just wondering if there is any hot keys to move the cursor to focus between the split windows back and forth quickly? Using mouse is kinda slow. And what is a hot key for deleting a line quickly? Thank you.

I am using Komodo 4.2.1 on Mac OS X, and I want to do remote debugging (only one user) on my RHEL3 server which runs PHP 4.3.2. I have not tested the connection because I can't get the server to load xdebug.so.

When I call `php -m`, I get:
Failed loading /usr/lib/php4/xdebug.so: /usr/lib/php4/xdebug.so: undefined symbol: php_sprintf

------------ How I installed xdebug.so ------------

[root@dbsvr php4]# wget http://downloads.activestate.com/Komodo/RemoteDebugging/4.2/Linux/Komodo...

Hi,

I need to make a UDP perl daemon which captures the request, creates a thread and passes the data to it. I have managed to do the basics using IO::Socket and it works fine. The problem is that it takes a lot of processing is i send around 50 messages to this daemon sequentially from another script in a for loop (also according to the message print only around 20 msg get processed per second). I feel it is somewhat on the slow side and can be improved. Appreciate any thoughts on this. The code is as follows ...


use Log::Dispatch;
use Log::Dispatch::File;
use IO::Socket;