Go to file
Michael Jennings e8fb85b56d Eterm.spec: Fix typo in %{_rel} definition 2020-03-03 10:33:47 -07:00
bg remove .cvsignore files 2011-06-12 21:38:37 +00:00
debian Typo in eterm-utils.1 2014-12-17 14:37:58 +09:00
doc doc typos: "occurances", "seperators" and "suppliment" 2014-11-29 16:27:10 +09:00
pix remove .cvsignore files 2011-06-12 21:38:37 +00:00
src src/*.c, Eterm.spec: Various build fixes 2020-02-28 17:06:54 -07:00
themes remove .cvsignore files 2011-06-12 21:38:37 +00:00
utils remove .cvsignore files 2011-06-12 21:38:37 +00:00
.gitignore Add some new stuff to ignore. Helpful on Cygwin. 2014-10-24 17:57:58 -07:00
CVS-README Tue Aug 13 22:55:58 2002 Michael Jennings (mej) 2002-08-14 03:01:48 +00:00
ChangeLog Patch from Pavel Sanda <ps@ucw.cz> to fix copy/paste behavior with 2014-03-26 09:00:45 -07:00
Eterm.spec Eterm.spec: Fix typo in %{_rel} definition 2020-03-03 10:33:47 -07:00
LICENSE Tue Jan 6 01:08:47 2009 Michael Jennings (mej) 2009-01-06 09:08:48 +00:00
Makefile.am Fri Aug 18 13:41:14 2006 Michael Jennings (mej) 2006-08-18 17:41:19 +00:00
README Mon Oct 30 07:45:16 PST 2000 Michael Jennings <mej@eterm.org> 2000-10-30 23:05:25 +00:00
ReleaseNotes This should bring all the docs up-to-date (finally!). Now back to fixing 1999-11-13 01:50:14 +00:00
ReleaseNotes.1 This should bring all the docs up-to-date (finally!). Now back to fixing 1999-11-13 01:50:14 +00:00
autogen.sh Thu Sep 1 02:12:29 2005 Michael Jennings (mej) 2005-09-01 06:12:32 +00:00
configure.ac Patch from Pavel Sanda <ps@ucw.cz> to fix copy/paste behavior with 2014-03-26 09:00:45 -07:00
reformat-code Mon Feb 6 17:15:49 2006 Michael Jennings (mej) 2006-02-06 22:16:50 +00:00

README

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.