I'm new to Go. I've installed ActiveGo. How do I get started?
The introduction will explain how your workspace is arranged. In case you missed it, your $GOPATH has already been set by the ActiveGo installer.
If you don't use Git already, you should install it and learn how to use it. Git is an essential supporting tool for coding in Go.
There's a simple HelloWorld program in the Go introduction.
ActiveGo sets up local documentation on your system as a document server. On the local ActiveGo documentation start page, there is an interactive Sandbox window labelled "Try Go". You will see the source code before it compiles. When you click "Run" the code compiles and displays the result in the box below the source code. There's a pull-down with a small set of sample Go snippets.
Can I have ActiveGo and another distribution of Go installed together?
The ActiveGo-beta will set GOROOT, GOPATH, and PATH variables. The Golang distribution will also set GOROOT and PATH.
-ActiveGo will always be the default version of Go if both are on the system due to the ways both Go versions set up PATH. Neither ActiveGo nor Golang Go will remove the other distribution from PATH.
-Any value in GOROOT will be overwritten by both versions of Go when they install. The last version to install will be set up as the root. If you remove a version of Go, you will need to re-install/repair the other one to ensure that GOROOT is correct before you start using it.
-GOPATH is your personal workspace. Your workspace should be usable with either version of Go.
Will Komodo work with Farsi, Hebrew or some Asian languages that are read right to left?
Komodo unfortunately does not work with right-to-left languages, as mentioned in our Komodo IDE release notes, due to a limitation in the text editor component.
What is the easiest way to rename a node to use the xip.io service?
This command works on most Micro-Cloud setups on VMware/Virtual Box where one can route to whatever is returned by `ifconfig eth0`.
Unfortunately the above won't work on EC2/Openstack installs where an external IP is
routed to the internal instance in a private network. So use the alternative command below:
Do I really need 735 PB to unzip the VMWare Stackato VM?
No you certainly do not. Windows zip program is interpreting the zip file incorrectly and is looking for far more space than it needs. Just download 7zip and use it to unzip your file.
Why won't my Node.js debugging work in Komodo any more?
Node.js was original designed with Posix systems in mind. It uses network calls not available on Windows systems. There was a port done in the open community which is not quite complete so sometimes processes are left running. The debugger thinks it has shut them down but it hasn't.
Open your Task Manager and kill any node.js processes still running.
When I try to install ActivePerl on Windows, it says it is not supported by my processor type. My system meets the ActiveState requirements. Why is it not recognized?
This message isn't an ActiveState error message. It comes from within the Microsoft Installation tool, and it's rather misleading. The processor isn't in fact the problem.
What the message really indicates is that you are attempting to install a 64-bit binary on a 32-bit version of Windows. This won't work. A 64-bit processor will run either 32-bit or 64-bit Windows, but MSI installers for 64-bit software will only install on 64-bit Windows.
Most users solve this by using the 32-bit x86 ActivePerl installer with a 32-bit Windows, however in cases where a full 64-bit x86_64 ActivePerl is necessary there is no alternative except to first upgrade to a 64-bit version of Windows.
After a Windows update, Komodo no longer works, and the log files are untouched. I'm seeing three messages in the event viewer complaining about missing assemblies. What can I do?
These are the event messages the question refers to:
This is one of those problems that a small number of Komodo users have
reported in the last month, but we haven't been able to duplicate. A bit
of research found forums suggesting people delete directories in the
Windows/SxS area, but that sounded risky. One of our customers found
more success by downloading and installing the free-as-in-beer
Visual Basic Studio 8 Express Edition.
Until anyone finds a problem with that, it sounds good. In the meantime
I'm reading up on the problem and brushing up on MSI Merge Modules.
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.
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
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?
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:
2. optionally reinstall Komodo to
C:\Program Files\ instead.