You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
I'm working on some deallocators now. The idea is that when Eterm exits and memory debugging is on, several routines get called to free the in-use memory (menus, font cache, etc.) that we still know about. Anything left after that would be either unavoidable leaks (like environment variables...read the putenv() man page sometime...sigh) or genuine memory leaks that need fixing. I'm down to about 4.5K of leftover malloc'd memory now. Making progress.... SVN revision: 3295
|23 years ago|
|bg||24 years ago|
|debian||23 years ago|
|doc||23 years ago|
|libmej||23 years ago|
|pix||24 years ago|
|src||23 years ago|
|themes||23 years ago|
|utils||23 years ago|
|.cvsignore||24 years ago|
|COPYING||24 years ago|
|CVS-README||24 years ago|
|ChangeLog||23 years ago|
|Eterm.spec.in||23 years ago|
|Makefile.am||23 years ago|
|README||24 years ago|
|ReleaseNotes||24 years ago|
|ReleaseNotes.1||24 years ago|
|acconfig.h||23 years ago|
|acinclude.m4||24 years ago|
|autogen.sh||24 years ago|
|configure.in||23 years ago|
|reformat-code||23 years ago|
|stamp-h.in||24 years ago|
Release notes for Eterm 0.9
- 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.
From the toplevel Eterm source tree directory:
After performing the build step above, run:
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
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.