Go to file
Michael Jennings db2f3e7394 Mon Jul 3 12:17:53 PDT 2000 Michael Jennings <mej@eterm.org>
Marius Gedminas <mgedmin@takas.lt> reported a couple of issues back
	when he was on his bug-spotting binge that I didn't have time to fix
	just then.  Well, now I've fixed them.  ~/.Eterm/user.cfg will now
	be found if there isn't a theme-specific one; this allows you to have
	a single user.cfg which specifies some options you want all your
	Eterms to have.

	Along those same lines, the action code now searches for duplicate
	bindings and changes the existing one rather than adding a new one
	to the end of the list.  This allows bindings in user.cfg to override
	those in theme.cfg (as they should).  Also, bindings are added in
	reverse order, so newer ones (like in user.cfg) take precedence over
	older ones (like in theme.cfg) if there is a conflict (e.g., if your
	theme.cfg binds "anymod button2" and user.cfg binds "ctrl button2,"
	user.cfg wins).


SVN revision: 2901
2000-07-03 19:08:41 +00:00
bg Some more. 2000-01-19 01:41:37 +00:00
debian This is minor, mostly temporary build stuff. dh.tar.gzis uncompressed in 2000-05-24 17:48:03 +00:00
doc Sat Jun 10 11:38:36 PDT 2000 Michael Jennings <mej@eterm.org> 2000-06-10 18:21:35 +00:00
libmej Mon Jul 3 12:17:53 PDT 2000 Michael Jennings <mej@eterm.org> 2000-07-03 19:08:41 +00:00
pix Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org> 2000-02-11 00:25:07 +00:00
src Mon Jul 3 12:17:53 PDT 2000 Michael Jennings <mej@eterm.org> 2000-07-03 19:08:41 +00:00
themes Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org> 2000-04-13 04:19:05 +00:00
utils Fri Jun 16 13:29:59 PDT 2000 Michael Jennings <mej@eterm.org> 2000-06-16 20:13:09 +00:00
.cvsignore Bleh. 1999-12-06 17:25:35 +00:00
COPYING Initial import of Eterm 0.8.9 sources 1999-08-17 23:01:18 +00:00
CVS-README Fri Jan 14 16:34:13 PST 2000 Michael Jennings <mej@eterm.org> 2000-01-15 00:37:22 +00:00
ChangeLog Mon Jul 3 12:17:53 PDT 2000 Michael Jennings <mej@eterm.org> 2000-07-03 19:08:41 +00:00
Eterm.spec.in Sun May 28 14:45:03 PDT 2000 Michael Jennings <mej@eterm.org> 2000-05-28 21:28:31 +00:00
Makefile.am This should bring all the docs up-to-date (finally!). Now back to fixing 1999-11-13 01:50:14 +00:00
README Fri Jan 21 18:40:13 PST 2000 Michael Jennings <mej@eterm.org> 2000-01-22 02:40:49 +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
acconfig.h Thu May 4 00:32:45 PDT 2000 Michael Jennings <mej@eterm.org> 2000-05-04 07:22:07 +00:00
acinclude.m4 Mon Oct 4 18:20:15 PDT 1999 Michael Jennings <mej@eterm.org> 1999-10-04 22:24:28 +00:00
autogen.sh These two files don't do much at the moment. I'm hoping someone else might 2000-03-30 02:37:01 +00:00
configure.in Mon Jun 26 16:54:04 PDT 2000 Michael Jennings <mej@eterm.org> 2000-06-26 23:37:05 +00:00
reformat-code Initial import of Eterm 0.8.9 sources 1999-08-17 23:01:18 +00:00
stamp-h.in Initial import of Eterm 0.8.9 sources 1999-08-17 23:01:18 +00:00

README

Release notes for Eterm 0.9
---------------------------

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
-------------
- The FAQ and message forum at http://eterm.i-docs.org/
- The man page at http://www.eterm.org/
- Running "Eterm --help" will show you the command line options.
- 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 EFNet IRC channel #E 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.