OpenEuphoria

OK, what exactly did you download? Was it the debian package? In that case, a lot of stuff (include files, demos, source, etc) goes there. The binaries go right into /usr/bin in that case, and you should be able to run them, since they would be in your path. The .bash_profile stuff is just to add something to your path.

It also adds man pages, and you should be able to view the documentation locally if you have something like dhelp installed. Try typing, for example, "man eui" and you should get a man page for the euphoria interpreter.

I downloaded the beta from main page, the 'test drive' link. Next, I tried to make sure to reduce user error instances. For instance, I left the Euphoria folder in /usr/share and made sure .bashrc was setup right.

PATH=$PATH:/usr/share/euphoria/bin export PATH EUDIR=/usr/share/euphoria

I also checked .bash_profile and profile to make sure they were empty (this shouldn't be a problem, after all, I created .bash_profile from scratch and .profile was empty in the first place. even in nautilus).

Try something like:

$ which eui 

And let us know what you get.

/usr/bin/eui

Also, try:

$ echo $PATH 

...and let us know if that includes whatever you put into .bash_profile.

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

But if you installed the debian package, you should be good to go. It automatically puts the binaries where you can run them, and adds an eu.cfg file to /etc/euphoria (IIRC), which is checked by default. So you should have access to the standard library by:

include std/... 

Note that you really don't need to set $EUDIR if you use a config (eu.cfg) file. It's actually easier, since editing a config file always takes immediate effect (as opposed to environment variables, which changes don't propagate to open shells).

Matt