old
/
eterm
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
185 Commits 2 Branches 0 Tags 2.6 MiB
C 92.9%
M4 3.1%
Roff 1.8%
Assembly 1%
Shell 0.6%
Other 0.6%
Go to file
Michael Jennings e64307644d Fri May 26 20:43:03 PDT 2000 Michael Jennings <mej@eterm.org> 
Okay, there are a few changes here.  First off, I made multi-byte font
	support the default now, as long as you have ISO 10646 fonts.  In
	order to do this, I made the default encoding type "Latin1" so as not
	to interfere with 8-bit ISO 8859-1 characters.  This means that if you
	relied on the default multi-byte encoding method to be SJIS, you'll
	need to update your theme files.

	I also set it up so that Eterm will ignore SIGHUP, at least until I do
	something with it (like reloading the theme or something).

	I fixed the proportional font size algorithm.  If there is more than
	a 3-pixel variance between the minimum and maximum sizes for glyphs in
	a proportional font, Eterm will set the size to 2 standard deviations
	above the average width.  This is so that they won't look so spread
	out and ugly, but it still doesn't look perfect.  Not much I can do on
	that front...terminals must have fixed-width columns.

	And then there's the biggie.  I put in the ability to configure the
	now-infamous font effects.  I left a black drop shadow in as the
	default, but you can now customize it via the --font-fx option or in
	the config file using "font effects <stuff>" in the attributes
	context.  You can even use "fx" instead of "effects" for short.

	So what goes in the <stuff> part?  Well, you have several options.
	To use a single-color outline, say "outline <color>".  Likewise, a
	single-color drop shadow is "shadow [corner] <color>"; "bottom_right"
	is the default corner if you don't specify one.  For a 3-D embossed
	look, "emboss <dark_color> <light_color>".  The opposite, a carved-
	out look, can be had with "carved <dark_color> <light_color>".  (Of
	course, with those last two, the 3-D look will only work if you
	choose the colors wisely.)

	Those are all the shortcuts.  The long way is to specify a series of
	corner/color pairs, like "tl blue" for top-left blue, or
	"bottom_right green".  You can abbreviate using "tl," "tr," "bl," or
	"br," or you can spell out "top_left," "top_right," "bottom_left," or
	"bottom_right."  If you omit a corner name, the first one defaults to
	top-left, the second to top-right, and so on as listed above.


SVN revision: 2714
 		2000-05-27 03:41:22 +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 Tue Mar 14 19:11:26 PST 2000 Michael Jennings <mej@eterm.org> 2000-03-15 03:17:45 +00:00
libmej Fri May 26 20:43:03 PDT 2000 Michael Jennings <mej@eterm.org> 2000-05-27 03:41:22 +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 May 26 20:43:03 PDT 2000 Michael Jennings <mej@eterm.org> 2000-05-27 03:41:22 +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 Tue May 2 16:56:47 PDT 2000 Michael Jennings <mej@eterm.org> 2000-05-02 23:46:08 +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 May 26 20:43:03 PDT 2000 Michael Jennings <mej@eterm.org> 2000-05-27 03:41:22 +00:00
Eterm.spec.in Thu Apr 27 19:54:28 PDT 2000 Michael Jennings <mej@eterm.org> 2000-04-28 02:42:26 +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 Fri May 26 20:43:03 PDT 2000 Michael Jennings <mej@eterm.org> 2000-05-27 03:41:22 +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.