Go to file
Michael Jennings c3f775c1b5 Mon Jun 11 17:49:55 PDT 2001 Michael Jennings <mej@eterm.org>
Okay, first off, I removed 3 scaled backgrounds.  See www.kainx.org or
	my post to enlightenment-devel for details.

	Second, I redid the default bindings for the mouse wheel.  Basically,
	the wheel alone will scroll by pages.  Ctrl+wheel will scroll by pages
	in groups of 5.  Shift+wheel will scroll by a single line.  If you
	hold down the Alt key, the same combinations will work the same way,
	but instead of scrolling within Eterm, they'll scroll the application
	in the terminal (by sending PgUp/PgDn and up/down arrows).  This works
	in less, bash, and any other application which groks those keys.

	I also added a --without-mousewheel option to configure that will turn
	off the default scrollwheel bindings.  Of course, you can always use
	action bindings in the config file to bind/rebind these any way you
	like.

	While I was at it, I found and fixed a bug in the handling of the
	Alt and Meta keys.

	I added a scroll() function to the script stuff which allows you to
	bind keys/buttons to scroll up and down.  While I was at it, I added
	comments to script.c for each function you can use.

	And finally, the config file parser was moved to libast.


SVN revision: 4806
2001-06-12 01:04:45 +00:00
bg Mon Jun 11 17:49:55 PDT 2001 Michael Jennings <mej@eterm.org> 2001-06-12 01:04:45 +00:00
debian changelog madness 2001-03-17 11:14:26 +00:00
doc This is work in progress, cleaning up the selection stuff. Still more to 2001-05-19 06:56:45 +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 Jun 11 17:49:55 PDT 2001 Michael Jennings <mej@eterm.org> 2001-06-12 01:04:45 +00:00
themes Wed May 9 17:18:11 PDT 2001 Michael Jennings <mej@eterm.org> 2001-05-10 00:20:15 +00:00
utils Mon Mar 5 13:38:01 PST 2001 Michael Jennings <mej@eterm.org> 2001-03-05 21:38:58 +00:00
.cvsignore Meh. 2001-01-10 21:13:14 +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 Jun 11 17:49:55 PDT 2001 Michael Jennings <mej@eterm.org> 2001-06-12 01:04:45 +00:00
Eterm-mdk.spec.in Fri May 4 23:56:12 PDT 2001 Michael Jennings <mej@eterm.org> 2001-05-05 06:57:28 +00:00
Eterm.spec.in Fri May 4 23:56:12 PDT 2001 Michael Jennings <mej@eterm.org> 2001-05-05 06:57:28 +00:00
Makefile.am Fix make distcheck. 2000-11-17 07:59:11 +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
acconfig.h Mon Jun 11 17:49:55 PDT 2001 Michael Jennings <mej@eterm.org> 2001-06-12 01:04:45 +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 11 17:49:55 PDT 2001 Michael Jennings <mej@eterm.org> 2001-06-12 01:04:45 +00:00
reformat-code Fri Sep 1 21:03:53 PDT 2000 Michael Jennings <mej@eterm.org> 2000-09-02 04:12:16 +00:00
stamp-h.in Initial import of Eterm 0.8.9 sources 1999-08-17 23:01:18 +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.