535 lines
21 KiB
HTML
535 lines
21 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
|
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>Eterm FAQ</TITLE>
|
|
</HEAD>
|
|
|
|
<BODY bgcolor="#ffffff" text="#000000" vlink="#3f3fff" link="#0000ff" alink="#000000">
|
|
|
|
<H1>Eterm FAQ</H1>
|
|
<P>
|
|
<H2>Contents</H2>
|
|
<P>
|
|
<UL>
|
|
<LI><A HREF="#q1">How do I know which version of Eterm I am running?</A>
|
|
<LI><A HREF="#q2">Why did you have to go and change all the options!?</A>
|
|
<LI><A HREF="#q3">Why isn't my .Xdefaults being parsed any more?</A>
|
|
<LI><A HREF="#q4">Well then why isn't the Eterm theme <TT>MAIN</TT> file being parsed?</A>
|
|
<LI><A HREF="#q5">Where do I find out what you've changed for each release?</A>
|
|
<LI><A HREF="#q6">What information/help files are in the Eterm distribution?</A>
|
|
<LI><A HREF="#q7">Do I need this file called <TT>Eterm-bg.tar.gz</TT>?</A>
|
|
<LI><A HREF="#q8">The man page is all wrong! What's up with that?</A>
|
|
<LI><A HREF="#q9">Why did the mouse selection thing suddenly quit working?</A>
|
|
<LI><A HREF="#q10">The docs keep mentioning blinking text, but I can't get it to work. What am I doing wrong?</A>
|
|
<LI><A HREF="#q11">How do I change the screen colors?</A>
|
|
<LI><A HREF="#q12">What's the deal with Backspace/Delete? Neither seems to work!</A>
|
|
<LI><A HREF="#q13">Why won't my Backspace work under Linux?</A>
|
|
<LI><A HREF="#q14">How do I change the key bindings in Eterm?</A>
|
|
<LI><A HREF="#q15">My keyboard has some extra keys. How can I use them in Eterm?</A>
|
|
<LI><A HREF="#q16">How does a program tell if it's running in an Eterm or an xterm?</A>
|
|
<LI><A HREF="#q17">How do I properly set <B><TT>$DISPLAY</TT></B> to the correct, full IP address from a shell?</A>
|
|
<LI><A HREF="#q18">Why isn't the <TT>-n (--name)</TT> option working?</A> (added 6 Sept 1997)
|
|
<LI><A HREF="#q19">Eterm doesn't work on my machine. Help!</A> (added 19 Sept 1997)
|
|
<LI><A HREF="#q20">Why is 0 sending a Ctrl-C?</A> (added 5 August 1998)
|
|
<LI><A HREF="#q21">What constitutes an Eterm theme?</A> (added 5 August 1998)
|
|
<LI><A HREF="#q22">How does Eterm determine which theme to use?</A> (added 5 August 1998)
|
|
<LI><A HREF="#q23">What does this accomplish?</A> (added 5 August 1998)
|
|
<!-- <LI><A HREF="#q"></A> -->
|
|
</UL>
|
|
|
|
<HR SIZE=5>
|
|
<H2>Q&A</H2>
|
|
<P>
|
|
<H3><A NAME="q1">How do I know which version of Eterm I am running?</A></H3>
|
|
<P>
|
|
Eterm always displays its current version at the top of the options list
|
|
on the usage screen. You can view the usage screen by envoking Eterm with
|
|
the <TT>-h</TT> or <TT>--help</TT> option. Also, you can place the current
|
|
version number in the Eterm title bar using the escape sequence "ESC[8n".
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q2">Why did you have to go and change all the options!?</A></H3>
|
|
<P>
|
|
There are several reasons we chose to do this:
|
|
<BR>
|
|
<OL>
|
|
<LI> To make Eterm's command-line option mechanisms be POSIX- and GNU-compliant.
|
|
<LI> To allow for shorter synonyms for the most frequently-used options.
|
|
<LI> We were sick of the obfuscated nature of the xterm options.
|
|
<LI> We felt like it.
|
|
</OL>
|
|
For those who don't know, POSIX-standard option syntax uses single-letter options
|
|
which can be combined on the command line (e.g., the "-xvf" in a tar command),
|
|
among other things. GNU-standard options (also known as "long options") begin
|
|
with two hyphens and make it very easy to tell what an individual option
|
|
controls (e.g., --background-pixmap, whose POSIX synonym is -P).
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q3">Why isn't my .Xdefaults being parsed any more?</A></H3>
|
|
<P>
|
|
This is another change made as of DR 0.6. Since it is <I>E</I>term (Enlightened term,
|
|
intended for use with <A HREF="http://www.enlightenment.org/" TARGET="_top">The
|
|
Enlightenment Window Manager</A>), we chose to have it read a config file
|
|
very similar to Enlightenment's own MAIN.
|
|
|
|
<P>
|
|
Eterm 0.7 has support for themes. (See the later question,
|
|
"<A HREF="#q21">What constitutes an Eterm theme?</A>", for more info
|
|
on themes.) By default, the <TT>make install</TT> will copy the themes
|
|
from the themes/* directories into the <TT>$libdir/Eterm/themes/</TT> directory
|
|
(<TT>/usr/local/lib/Eterm/themes</TT> by default). It will no longer read
|
|
<TT>~/.Eterm/MAIN</TT>, but instead will look for the Eterm theme if no
|
|
theme is specified on the command line.</P>
|
|
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q4">Well then why isn't the Eterm theme <TT>MAIN</TT> file being parsed?</A></H3>
|
|
<P>
|
|
The most likely cause of this (besides not having one :-) is not having the
|
|
proper "magic number" line at the top of your config file. As of DR 0.6a,
|
|
the first line of your config file must look like:<BR>
|
|
<PRE>
|
|
<Eterm-0.6a>
|
|
</PRE>
|
|
|
|
<P>
|
|
This "magic number" mechanism prevents Eterm from trying to read an Enlightenment
|
|
config file as its own, and it may provide backward compatibility in the future.
|
|
The "0.6a" part represents the version of Eterm for which the config file was
|
|
written (without the "DR" if there is one).
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q5">Where do I find out what you've changed for each release?</A></H3>
|
|
<P>
|
|
There is a file called <TT>RELNOTES.Eterm</TT> in the base directory of each
|
|
Eterm distribution. Those release notes give information about what changes
|
|
were made in each release, plans for future changes, etc.
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q6">What information/help files are in the Eterm distribution?</A></H3>
|
|
<P>
|
|
Here is a list:
|
|
<UL>
|
|
<LI> doc/FAQ -- A preliminary Eterm FAQ. This document will soon replace it.
|
|
<LI> doc/colortest.sh -- A script to demonstrate Eterm's color capabilities.
|
|
<LI> doc/Eterm.ref -- Eterm technical reference. Exhaustive list of all supported escape sequences.
|
|
<LI> doc/menu.sh -- A script to demonstrate Eterm's menubar code.
|
|
<LI> doc/Eterm.tcap -- Sample Eterm termcap file.
|
|
<LI> doc/Eterm.ti -- Sample Eterm terminfo file. Compile with <TT>tic</TT>.
|
|
<LI> doc/Eterm.help -- Output of <TT>Eterm --help</TT> (until we get a new man page).
|
|
<LI> doc/Eterm.1 -- Old Eterm man page. Does not reflect changes in DR 0.6.
|
|
<LI> RELNOTES.Eterm -- Eterm release notes. Read this!!
|
|
<LI> INSTALL -- A script that does the configure, compile, link, and install for you.
|
|
</UL>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q7">Do I need this file called <TT>Eterm-bg.tar.gz</TT>?</A></H3>
|
|
<P>
|
|
One of Eterm's most notable features is its ability to put images (called pixmaps by
|
|
convention) in the background of your terminal windows. <TT>Eterm-bg.tar.gz</TT>
|
|
(obtainable from any Eterm site) contains about 14 Meg worth of cool pixmaps to
|
|
try. It's completely optional. If you do get it, be sure to untar it into your
|
|
home directory. It puts the images in <TT>.Eterm/pix/</TT> underneath wherever
|
|
you install it. I also left the <TT>.xvpics</TT> directory intact, so you can use
|
|
the Visual Schnauzer to preview the pixmaps.
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q8">The man page is all wrong! What's up with that?</A></H3>
|
|
<P>
|
|
The man page for Eterm DR 0.6 and later is not finished yet. Stay tuned to these
|
|
pages. I'll post it here as soon as it's ready.
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q9">Why did the mouse selection thing suddenly quit working?</A></H3>
|
|
<P>
|
|
Make sure that mouse reporting is actually turned off. Unfortunately, some editors
|
|
do not properly turn off mouse reporting when they are abnormally terminated. The
|
|
tcsh shell may also use mouse reporting unless explicitly turned off. You can check
|
|
this by trying the selection/cut/paste while holding down Alt or Shift. See the
|
|
Technical Reference (<TT>doc/Eterm.ref</TT>) for more detailed information.
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q10">The docs keep mentioning blinking text, but I can't get it to work. What am I doing wrong?</A></H3>
|
|
<P>
|
|
You aren't doing anything wrong. Eterm does not support, and probably never will
|
|
support, blinking text. Instead (assuming NO_BRIGHTCOLOR is *not* defined during
|
|
compilation), Eterm uses the bold and blink attributes to provide high-intensity
|
|
versions of the foreground and background colors respectively. In general,
|
|
colors 0-7 are the low-intensity colors, and colors 8-15 are the corresponding
|
|
high-intensity colors. (So color 8 is a "bold" color 0, color 9 is a "bold"
|
|
color 1, etc.) It is worth noting that some programs break this convention and
|
|
use colors 8-15 to provide 16 total colors, none of which bear any relationship
|
|
to any other based on their color number.
|
|
|
|
<P>
|
|
Related to this issue is the question of how the default foreground and
|
|
background colors are treated (those specified by the -f (--foreground-color)
|
|
and -b (--background-color) options) with respect to the bold and blink
|
|
attributes. In the simplest (and most common) case, the fg/bg colors each match
|
|
one of the low-intensity colors (0-7). If this is true, the bold/blink
|
|
attributes (respectively) activate the corresponding high-intensity color
|
|
(8-15).
|
|
|
|
<P>
|
|
If this is not the case, and either the foreground color or the background
|
|
color does not match any of the 8 low-intensity colors, slightly different
|
|
action must be taken. In the former case, the bold foreground is simulated
|
|
using an overstrike mechanism <FONT COLOR="#ff0f0f">*</FONT>. In the
|
|
latter case, the blink attribute is simply ignored.
|
|
|
|
<P>
|
|
<FONT COLOR="#ff0f0f">*</FONT> This feature is dependent upon NO_BOLDOVERSTRIKE
|
|
not being defined during compile. Furthermore, its use is discouraged and
|
|
unsupported, as it tends to create "pixel droppings."
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q11">How do I change the screen colors?</A></H3>
|
|
<P>
|
|
You can change the colors 0-15 in your Eterm configuration file. These settings,
|
|
taken from <TT>themes/Eterm/MAIN</TT>, are Rasterman's colors which he says work well
|
|
for displaying ANSI art:
|
|
|
|
<PRE>
|
|
color 0 0 0 0
|
|
color 1 0xaa 0 0
|
|
color 2 0 0210 0
|
|
color 3 0xaa 0x55 0x22
|
|
color 4 0 0 0xaa
|
|
color 5 0xaa 0 0xaa
|
|
color 6 0 0xaa 0xaa
|
|
color 7 0xaa 0xaa 0xaa
|
|
color 8 0x44 0x44 0x44
|
|
color 9 0xff 0x44 0x44
|
|
color 10 0x44 0xff 0x44
|
|
color 11 0xff 0xff 0x44
|
|
color 12 0x44 0x44 0xff
|
|
color 13 0xff 0x44 0xff
|
|
color 14 0x44 0xff 0xff
|
|
color 15 #ffffff
|
|
</PRE>
|
|
|
|
<P>
|
|
The syntax for this section is discussed in <TT>themes/Eterm/MAIN</TT>.
|
|
|
|
<P>
|
|
You can also change individual colors on the command line, using the <TT>--color<I>N</I></TT>
|
|
options (where <I>N</I> is the number of the color you wish to change). The value can be
|
|
either a color name or an RGB triple. For example, <TT>--color5=blue</TT> or
|
|
<TT>--color1="#ff0000"</TT>.
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q12">What's the deal with Backspace/Delete? Neither seems to work!</A></H3>
|
|
<P>
|
|
The Backspace/Delete problem has plagued UNIX for quite some time now, and there are
|
|
no easy answers. This FAQ covers how Eterm handles the two keys; however, detailed
|
|
explanations of <TT>xmodmap</TT>, <TT>stty</TT>, and so forth are beyond its scope.
|
|
The appropriate man pages should be consulted.
|
|
|
|
<P>
|
|
First, I'll assume that the Backspace key on your keyboard corresponds to the Backspace
|
|
keysym under X. (This is not always the case. See the next question for more details
|
|
on this.) There are two standard values that the Backspace key sends: Ctrl-H ("^H")
|
|
and Ctrl-? ("^?"). Eterm inherits the "erase" stty setting from the terminal from
|
|
which it is started. If it is not started from a terminal (e.g., if it were started
|
|
from a window manager button or pull-down menu, or a remote shell), Eterm defaults
|
|
to the value of CERASE (defined in <termios.h>). This may not be the same
|
|
as the stty settings of your terminal.
|
|
|
|
<P>
|
|
When starting a new Eterm, you can set the desired value before calling Eterm:
|
|
|
|
<PRE>
|
|
$ stty erase ^H
|
|
$ Eterm
|
|
</PRE>
|
|
|
|
or
|
|
|
|
<PRE>
|
|
$ stty erase ^?
|
|
$ Eterm
|
|
</PRE>
|
|
|
|
<P>
|
|
Remember, you can generate either value using Backspace and Ctrl/Shift-Backspace. You
|
|
can also toggle which key is which using the "ESC[36h" and "ESC[36l" escape sequences.
|
|
|
|
<P>
|
|
In an existing Eterm, use these commands:
|
|
|
|
<PRE>
|
|
$ stty erase ^H
|
|
$ echo -n "^[[36h"
|
|
</PRE>
|
|
|
|
or
|
|
|
|
<PRE>
|
|
$ stty erase ^?
|
|
$ echo -n "^[[36l"
|
|
</PRE>
|
|
|
|
<P>
|
|
Of course, there are other Backspace-related problems. For example, some editors
|
|
use termcap/terminfo, but there are some that expect Backspace == ^H regardless.
|
|
And then there's GNU Emacs, which binds ^H to help.... My personal solution is
|
|
to always use ^H for backspace, and add this line to my <TT>.emacs</TT> file:
|
|
|
|
<PRE>
|
|
(global-set-key "\C-h" 'delete-backward-char)
|
|
</PRE>
|
|
|
|
<P>
|
|
This should cover the Backspace problems. Remember that if you use ^? for Backspace,
|
|
you'll need to change the <TT>doc/Eterm.ti</TT> and <TT>doc/Eterm.tcap</TT> to
|
|
reflect this.
|
|
|
|
<P>
|
|
The Delete key (which is supposed to correspond to ^?) has problems of its own. In
|
|
an effort to avoid excessive confusion (yeah, right :-) between Backspace and
|
|
Delete, Eterm assigns "ESC[3~" to the Delete key, which is the vt100 sequence
|
|
for Execute.
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q13">Why won't my Backspace work under Linux?</A></H3>
|
|
<P>
|
|
Apparently, the XFree86 server elects to map the Backspace key as Delete to match
|
|
the Linux console. Besides complaining to the Linux and XF86 people, here's
|
|
what you can do about it:
|
|
|
|
<OL>
|
|
<LI> Use <TT>xmodmap</TT> to correct the Backspace mapping. Add this line to your <TT>~/.Xmodmap</TT>
|
|
file:
|
|
|
|
<PRE>
|
|
keycode 22 = BackSpace
|
|
</PRE>
|
|
|
|
Use <TT>xev</TT> to change the keycode to properly match your machine if needed. This
|
|
will also fix the BackSpace problem with Motif applications, like Netscape.
|
|
<LI> Remap the Eterm keybindings as described in the next answer. You will lose
|
|
the Ctrl/Shift-Backspace and escape sequence toggling functionality discussed
|
|
in the previous answer.
|
|
</OL>
|
|
<P>
|
|
Congratulations! Your Backspace now works as described in the previous answer, so
|
|
start from there.
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q14">How do I change the key bindings in Eterm?</A></H3>
|
|
<P>
|
|
You must compile Eterm with KEYSYM_RESOURCE defined to change key bindings.
|
|
Assuming you've done this, you can change the keystrings associated with
|
|
keysyms 0xFF00 - 0xFFFF (special keys only) in your Eterm config file.
|
|
|
|
<P>
|
|
Here is a sample set of keysym attributes included in the tn3270 theme:
|
|
|
|
<PRE>
|
|
# Delete - ^D
|
|
keysym 0xFFFF "\004"
|
|
|
|
# Left - ^B
|
|
keysym 0xFF51 "\002"
|
|
# Right - ^F
|
|
keysym 0xFF53 "\006"
|
|
# Up - ^P
|
|
keysym 0xFF52 "\020"
|
|
# Down - ^N
|
|
keysym 0xFF54 "\016"
|
|
# Home - ^A
|
|
keysym 0xFF50 "\001"
|
|
# End - ^E
|
|
keysym 0xFF57 "\005"
|
|
|
|
# F1 - F12
|
|
keysym 0xFFBE "\e1"
|
|
keysym 0xFFBF "\e2"
|
|
keysym 0xFFC0 "\e3"
|
|
keysym 0xFFC1 "\e4"
|
|
keysym 0xFFC2 "\e5"
|
|
keysym 0xFFC3 "\e6"
|
|
keysym 0xFFC4 "\e7"
|
|
keysym 0xFFC5 "\e8"
|
|
keysym 0xFFC6 "\e9"
|
|
keysym 0xFFC7 "\e0"
|
|
keysym 0xFFC8 "\e-"
|
|
keysym 0xFFC9 "\e="
|
|
|
|
# map Prior/Next to F7/F8
|
|
keysym 0xFF55 "\e7"
|
|
keysym 0xFF56 "\e8"
|
|
</PRE>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q15">My keyboard has some extra keys. How can I use them in Eterm?</A></H3>
|
|
<P>
|
|
The proper way to do this is to use <TT>xmodmap</TT> to remap the keys needed.
|
|
Consult the appropriate man page, as a discussion of <TT>xmodmap</TT> usage
|
|
is beyond the scope of this FAQ.
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q16">How does a program tell if it's running in an Eterm or an xterm?</A></H3>
|
|
<P>
|
|
It is useful to know whether or not you are in an xterm or an Eterm (or
|
|
another terminal emulator that supports color), for purposes of setting
|
|
color variables and so forth. To this end, Eterm always sets and exports
|
|
the <B><TT>$COLORTERM</TT></B> environment variable, so you can use
|
|
<TT>test</TT> to see if it's set. Many programs (mutt, jed, slrn, etc.)
|
|
perform this test for you to determine whether or not to use color.
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q17">How do I properly set <B><TT>$DISPLAY</TT></B> to the correct, full IP address from a shell?</A></H3>
|
|
<P>
|
|
You must have compiled Eterm with DISPLAY_IS_IP and ENABLE_DISPLAY_ANSWER defined. It
|
|
is also wise to define ESCZ_ANSWER properly, or the provided shell code samples
|
|
will not work. (You'll need to use <B><TT>$COLORTERM</TT></B> to determine if you
|
|
are using an Eterm.)
|
|
|
|
<P>
|
|
Here are a couple shell script samples that will properly set your
|
|
<B><TT>$DISPLAY</TT></B>, first for Bourne/POSIX-compatible shells,
|
|
then for csh-compatible shells.
|
|
|
|
<PRE>
|
|
#!/bin/sh
|
|
# If $TERM is not set, set it to xterm
|
|
[ ${TERM:-empty} = empty ] && TERM=xterm
|
|
|
|
# If it's an xterm, see if it's an Eterm
|
|
if [ ${TERM:-foo} = xterm ]; then
|
|
stty -icanon -echo min 0 time 15
|
|
echo -n '^[Z'
|
|
read term_id
|
|
stty icanon echo
|
|
|
|
# If it's an Eterm, get $DISPLAY from it.
|
|
if [ "$term_id" = '^[[?1;2C' -a ${DISPLAY:-empty} = empty ]; then
|
|
echo -n '^[[7n'
|
|
read DISPLAY
|
|
fi
|
|
fi
|
|
----- 8< ----- cut here ----- 8< -----
|
|
#!/bin/csh
|
|
# If $TERM is not set, set it to xterm
|
|
if ( !(${?TERM}) ) then
|
|
TERM = xterm
|
|
endif
|
|
|
|
# If it's an xterm, see if it's an Eterm
|
|
if ( ${TERM} =~ xterm ) then
|
|
stty -icanon -echo min 0 time 15
|
|
echo -n '^[Z'
|
|
set term_id=$<
|
|
stty icanon echo
|
|
if ( "${term_id}" == "^[[?1;2C" && ${?DISPLAY} == 0 ) then
|
|
echo -n '^[[7n'
|
|
setenv DISPLAY "$<"
|
|
endif
|
|
endif
|
|
</PRE>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q18">Why isn't the <TT>-n (--name)</TT> option working?</A></H3>
|
|
<P>
|
|
This is most often due to the fact that the MAIN file distributed with
|
|
some versions of Eterm contains lines that set the <TT>title</TT> and
|
|
<TT>iconname</TT> attributes. If you comment these lines out, the <TT>-n
|
|
(--name)</TT> option will set the title and icon name if they are not
|
|
otherwise explicitly assigned on the command line.
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q19">Eterm doesn't work on my machine. Help!</A></H3>
|
|
<P>
|
|
One of the primary goals of the Eterm project is portability. We do our
|
|
best to write portable code, but we only have a limited number of platforms
|
|
on which we have accounts. Therefore, you as the end user are a vital part
|
|
of the testing and debugging process.
|
|
<P>
|
|
If you run into problems with Eterm, please go through the steps outlined
|
|
<A HREF="index.html#contact">here</A>. If you make it to the last step
|
|
(going in order, of course) with no luck, please do the following:</P>
|
|
<OL>
|
|
<LI> Comment out line 41 of <TT>src/feature.h</TT> where NDEBUG is defined.
|
|
<LI> Recompile Eterm.
|
|
<LI> Run the new copy of Eterm and mail the output to me (<I>mej@eterm.org</I>).
|
|
</OL>
|
|
This is the only way we can get the information we need about where the
|
|
program is when it runs into problems, or what privileges it has, or
|
|
whatever. If you do not do this, we cannot help you.
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q20">Why is 0 sending a Ctrl-C?</A></H3>
|
|
<P>
|
|
This problem was reported by Charles Hagenbuch <chuck@athera.ml.org>. I'm not sure
|
|
why it happens, but according to Chuck, <TT>stty sane</TT> fixes it.</P>
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q21">What constitutes an Eterm theme?</A></H3>
|
|
<P>
|
|
An Eterm theme consists of a primary configuration file, always called
|
|
"MAIN", residing in a directory bearing the same name as the
|
|
theme. This directory must be a child of one of the directories
|
|
specified by <TT>CONFIG_SEARCH_PATH</TT> in <TT>src/feature.h</TT>, in
|
|
the environment variable defined by <TT>PATHENV</TT> in <TT>src/feature.h</TT>,
|
|
or in the default PATH. The theme may also contain additional configuration
|
|
files referenced by the primary MAIN file, pixmaps, menu files, documentation,
|
|
etc., which are allowable as extensions to the minimum requirement of an
|
|
Eterm theme.
|
|
|
|
<P>
|
|
By convention, Eterm themes should be stored under
|
|
<TT>~/.Eterm/themes/<theme_name>/</TT> or
|
|
<TT>$libdir/themes/<theme_name></TT>
|
|
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q22">How does Eterm determine which theme to use?</A></H3>
|
|
<P>
|
|
<OL TYPE=1>
|
|
<LI>If the <TT>-t</TT> or <TT>--theme</TT> option is specified on the
|
|
command line, Eterm will search for, and use if found, the specified
|
|
theme.
|
|
<LI>Eterm will check to see if it is running under Enlightenment. If
|
|
it is, it will query Enlightenment for the current theme name.
|
|
It will then search for, and use if found, an Eterm theme by the
|
|
same name. (NOTE: This is contingent on Enlightenment having
|
|
this capability, so this will not work yet.)
|
|
<LI>Eterm will search for, and use if found, a theme called Eterm.
|
|
<LI>Eterm will search for, and use if found, a theme called DEFAULT.
|
|
<LI>As a last resort, Eterm will search for, and use if found, a
|
|
compatible MAIN file. (Recall that this is not a valid Eterm theme.)
|
|
</OL>
|
|
<BR><BR>
|
|
<HR SIZE=3 WIDTH=80%>
|
|
<H3><A NAME="q23">What does this accomplish?</A></H3>
|
|
<P>
|
|
This proposal fulfills both of the primary goals regarding theme
|
|
support. On the one hand, it allows for things like "Eterm -t tn3270",
|
|
where <TT>.../tn3270/MAIN</TT> would contain color definitions,
|
|
keysym definitions, etc. which would be beneficial to tn3270, but
|
|
perhaps detrimental to other applications.
|
|
|
|
<P>
|
|
On the other hand, it provides Enlightenment theme authors a relatively-
|
|
transparent mechanism for extending the look and feel of their E theme
|
|
to their Eterm windows.
|
|
<BR><BR>
|
|
|
|
<HR SIZE=3>
|
|
<TABLE>
|
|
<TR>
|
|
<TD ALIGN=middle VALIGN=middle><A HREF="http://www.nu-media.net/" TARGET="_top"><IMG ALIGN=middle SRC="/pics/nupower.gif" WIDTH=110 HEIGHT=60 ALT="[Powered by Nu-Media Net!]"></A></TD>
|
|
<TD ALIGN=middle VALIGN=middle><FONT SIZE=2>
|
|
Copyright © 1997-1995, Michael Jennings. All rights worth squat. These pages are guaranteed to be
|
|
100% SPAM(tm)-free or your money back!
|
|
</TD>
|
|
</TR>
|
|
</TABLE>
|
|
<BR>
|
|
<I>Last modified -- Wednesday, 05 August 1998, 21:19:35 EDT</I><BR>
|
|
|
|
</FONT>
|
|
</BODY>
|
|
|
|
</HTML>
|
|
|