Go to file
Michael Jennings 607268f595 Mon Mar 6 21:11:13 PST 2000 Michael Jennings <mej@eterm.org>
Added a new option.  -0 (that's a zero) or --itrans will invoke the
	immotile optimization for transparency, so named because it works best
	on windows that don't move around much on the desktop.  It works even
	better for windows that are sticky between desktops.  So if you have
	logging windows (running tail -f and the like) that are shaded/tinted,
	you definitely want to have this.  It will even benefit ordinary Eterm
	windows, provided you don't move them around a lot.  Eterms that do
	not change desktops may be better off with the other way; Eterms that
	are not shaded or tinted at all will not behave any differently.

	Here's the technical explanation for those who are interested.  The
	old (and still the default) behavior is for Eterm to check to see if
	any color modifiers are applied to the image_bg class, and if so, to
	make a copy of the *entire* desktop image which is then shaded/tinted
	appropriately.  It then snapshots a portion of that for the actual
	background.  This way, if the Eterm window is moved, all the shading
	and tinting will have already been done, so all it has to do is grab
	another portion of the desktop and use it.  However, this involves a
	LOT of calculations (one per pixel of the desktop pixmap) on startup
	and at every desktop switch.

	The immotile optimization is intended to reverse that logic by
	optimizing for windows that do not move (hence the term "immotile").
	It takes the snapshot of the desktop pixmap and applies any shading
	or tinting *after* taking the portion it needs.  This requires much
	fewer calculations on startup and when changing desktops, but the
	entire set of calculations must be repeated whenever the window is
	moved.  This is fine for small windows or windows that don't move
	very often, but that's not always the case.  So it is to your
	advantage to pick one or the other depending on how you use each
	particular theme or window.

	Two notes.  One, keep in mind that the -0/--itrans option doesn't
	*activate* transparency; you still need -O/--trans for that.  Two,
	this does not affect Eterms with no color modifiers applied to the
	background.  In that case, Eterm still references the existing
	desktop pixmap to save memory.

SVN revision: 2191
2000-03-07 05:30:33 +00:00
bg Some more. 2000-01-19 01:41:37 +00:00
debian more preliminary assimilation 1999-12-19 21:08:32 +00:00
doc Tue Feb 15 19:31:04 PST 2000 Michael Jennings <mej@eterm.org> 2000-02-16 03:37:34 +00:00
libmej Thu Mar 2 21:40:09 PST 2000 Michael Jennings <mej@eterm.org> 2000-03-03 05:43:53 +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 Mar 6 21:11:13 PST 2000 Michael Jennings <mej@eterm.org> 2000-03-07 05:30:33 +00:00
themes Wed Mar 1 18:37:18 PST 2000 Michael Jennings <mej@eterm.org> 2000-03-02 03:31:41 +00:00
utils Thu Feb 17 15:13:20 PST 2000 Michael Jennings <mej@eterm.org> 2000-02-17 23:15:19 +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 Mar 6 21:11:13 PST 2000 Michael Jennings <mej@eterm.org> 2000-03-07 05:30:33 +00:00
Eterm.spec.in RH fixes. 2000-02-01 20:17:08 +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 Fri Feb 18 21:09:29 PST 2000 Michael Jennings <mej@eterm.org> 2000-02-19 06:29:37 +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 Tue Aug 17 18:06:01 PDT 1999 Michael Jennings <mej@eterm.org> 1999-08-18 01:12:47 +00:00
configure.in Thu Mar 2 09:47:30 PST 2000 Michael Jennings <mej@eterm.org> 2000-03-02 17:48:30 +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


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.

- 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:

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.) :-)


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.