As of 17 August 1999, Eterm is now available via anonymous CVS from
cvs.enlightenment.org.  If you don't know how to use CVS, don't use
it.  The authors, of course, don't guarantee anything whatsoever about
Eterm being functional; we guarantee even less if you get it from CVS.
We try to remember to test things before we commit them, but we make
no promises. :-)

To connect to the enlightenment CVS server, you should have the latest
version of CVS installed. If you don't have the very latest version of
CVS installed, check out How to get CVS. To connect to the CVS server
using the UNIX client you will need to set your environment variable
appropriately:

bash/ksh/sh users:
 export CVSROOT=":pserver:anonymous@cvs.enlightenment.org:/cvsroot/enlightenment"
or csh/tcsh users:
 setenv CVSROOT ":pserver:anonymous@cvs.enlightenment.org:/cvsroot/enlightenment"

At this point, you'll need to run the following command (only the
FIRST time you check out the source code should you have to run this
command):

 cvs login

You'll get back a prompt that looks something like this:

 (Logging in to anonymous@cvs.enlightenment.org)
 CVS password:

At this point you can just hit enter. You should only have to do this
ONCE when you first check out source on a machine.  Once you've gotten
this far, the rest is just a matter of downloading, compiling, and
installing.  To check out source code for the first time, you use the
following command:

 cvs -z3 co Eterm

This will check out the latest development version of Eterm.  You can
also check out particular versions of Eterm, back as far as 0.8.9, by
using the version number as a tag (with hyphens instead of dots), like
so:

 cvs -z3 co -r Eterm-0-8-10 Eterm

Once you have checked out the source code, you can keep your source
tree up-to-date by using:

 cvs -z3 update -Pd Eterm

There are other modules in Enlightenment's CVS tree, including e,
imlib, fnlib, esound, audiofile, epplets, imlib2, eConfig, eplay,
va-anim, notgame, pesh, and efm.

After checking out or updating the source tree from CVS, you need to
build it.  The process is identical to the normal ./configure, make,
make install routing, except that you run "autogen.sh" rather than
"configure."  You pass the same options to autogen.sh as you did to
configure, like --prefix.  autogen.sh will pass these options along to
configure.  Once that is complete, simply run "make" and "make
install" as normal.

Eterm 0.9 README
----------------

Software Requirements
---------------------
- Version 11 of the X Window System.  I believe Release 4 is the minimum
  required, but R6 is highly recommended.
- The Imlib image library.  Visit http://www.enlightenment.org/ to download it
  or for more information.
- Eterm will work with any window manager (or no window manager at all), but it
  is designed to work best with Enlightenment.  Some features (like auto mode
  and similar IPC-based functions) will not work with other window managers, and
  other WM-dependent features (like desktop selection/switching) may or may not
  work.  That's life.

Documentation
-------------
- Running "Eterm --help" will show you the command line options.
- "man Eterm"
- The online FAQ's at and man pages at http://www.eterm.org/docs/
- The Technical Reference, also at the above web site, if you want more
  technical details about Eterm.

Building Eterm
--------------

From the toplevel Eterm source tree directory:

  ./configure
  make

Installing Eterm
----------------

After performing the build step above, run:

  make install

It is very important that you perform the "make install" step rather than simply
copying the binary into place.  The install routine does a lot more, and Eterm
will not run properly unless you perform a proper installation.

On some systems, you may need to install Eterm setuid root in order for it
to appear in a "w" or "who" listing.  This includes Debian Linux and HP-UX.
Redhat Linux and Solaris are known to not require setuid root.  If you need
to install Eterm setuid root, here's how:

  chown root /usr/local/bin/Eterm
  chmod u+s /usr/local/bin/Eterm

If you installed into a location other than /usr/local, change the above
paths appropriately.

Standard Disclaimer
-------------------

The authors don't take any responsibility for any damage this program
may do. We are doing this in our spare time. If you don't like this
program, don't use it.

Eterm was originally based on rxvt, but has been extensively modified.  In
its current form, most parts of Eterm bear little or no resemblence to rxvt (all
the cool parts.) :-)

Troubleshooting
---------------

Eterm has its own built-in debugging system which is enabled by the --debug
option on the command line.  Use --debug 2 to start with; you can go all the
way up to level 4 debugging.  Level 5 debugging slows things down a lot and is
disabled by default.  Only serious developers should touch that one.

Eterm is also capable to using gdb, dbx, and other tools to generate a stack
trace of itself when it crashes.  This information will help developers find
the problem.  Make sure that you compiled Eterm with the "-O0 -g3" compiler
flags (for gcc, or the equivalent flags for your compiler) if you choose to
submit a stack trace.

You'll also find people on the IRC channel #E (now on the OpenProjects
IRC Network at irc.openprojects.net) who might be able to answer your
questions, but please be sure you've read all the documentation
mentioned above before asking a question there.