Go to file
Michael Jennings d2ca8950e1 Fri Feb 18 21:09:29 PST 2000 Michael Jennings <mej@eterm.org>
Okay, I've added a new option to configure.  --config-buffer-size=NNNN
	will set the theme parser's line buffer size.  What does this mean?
	Well, this determines how big a line being parsed can get at any one
	stage of parsing.  So if you use %dirscan() on a large directory, or
	you use %random() on a large list, or you simply have some very large
	lines in your config file, making this buffer size larger will enable
	them to be handled.  The down side to this is that your Eterms will
	appear to take up more memory.  In reality they don't, since all that
	memory gets freed, but it isn't returned to the OS until Eterm exits,
	and the RSS won't go down unless part or all of Eterm is swapped out
	by the OS.  So you've been warned. :-)

	For those who didn't go digging by themselves, what I added yesterday
	were three new builtin functions:

	%get(variable)         Retrieves the value of a theme variable
	%put(variable value)   Sets the value of a theme variable
	%put(variable)         Removes a theme variable
	%dirscan(directory)    Returns a list of the files in a directory

	Everything here should be fairly self-explanatory.  The variables
	are internal to Eterm.  They will last until Eterm exits, so you
	can refer to them in later theme files, unless of course you call
	%put() with a variable but no value (which removes the variable).
	Also note that %dirscan() returns only the filenames, not the
	full pathnames.  This is for two reasons:  One, you already know the
	path to the file since you specified it.  Two, it enables handling of
	directories with larger numbers of files since the path isn't
	uselessly duplicated for each entry it generates.

	These new functions will be the backbone for a new random background
	system since the *.list files are rather clumsy in a lot of ways.  I
	am not yet sure how it will work exactly, but I know I'll need these
	functions to do it. :-)


SVN revision: 2104
2000-02-19 06:29:37 +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 Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org> 2000-02-11 00:25:07 +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 Fri Feb 18 21:09:29 PST 2000 Michael Jennings <mej@eterm.org> 2000-02-19 06:29:37 +00:00
themes Tue Feb 15 19:31:04 PST 2000 Michael Jennings <mej@eterm.org> 2000-02-16 03:37:34 +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 Fri Feb 18 21:09:29 PST 2000 Michael Jennings <mej@eterm.org> 2000-02-19 06:29:37 +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 Fri Feb 18 21:09:29 PST 2000 Michael Jennings <mej@eterm.org> 2000-02-19 06:29:37 +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.