Added a new --pipe-name option to allow Eterm to read from a console
device/tty/pipe other than /dev/console. This is useful for folks on
Debian, where "console" messages actually go to the /dev/xconsole
named pipe rather than to /dev/tty0.
SVN revision: 2212
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
Tom Gilbert <gilbertt@tomgilbert.freeserve.co.uk> spotted a fallback
issue with colors which I have now fixed. Tom, your e-mail address is
too damned long. Just thought you should know.
SVN revision: 2181
I did some optimizations for expose handling and full-screen redraws.
It will have a greater impact on those who don't use double buffering.
:-)
SVN revision: 2180
This fixes yet another resize-to-crash bug, this time with various
applications which use the secondary screen (mutt, mc, vim, etc.).
The fix is deceptively simple and does not convey the fact that it
took around 3 hours to track this bastard down. Credit to Marc Merlin
<marc@merlins.org> for first pointing this out and for helping me
track it down. And credit to Gray Watson for dmalloc, which has saved
my ass once again.
SVN revision: 2172
I'm still not done with the commenting work I've been doing, but I've
made some fixes, so I figured it was time to commit what I've done so
far.
I've added support for multi-byte selection/pastes from programs like
Netscape, thanks in part to a patch from Yasuyuki Furukawa
<yasu@on.cs.keio.ac.jp>. I've also applied a bugfix for pty
allocation on Irix from David Kaelbling <drk@sgi.com>, a display
bugfix pointed out by Valdis Kletnieks <Valdis.Kletnieks@vt.edu>, and
a fix for a missing menu in the auto theme discovered by someone on
IRC.
I've also added quite a few comments to term.c to help people grok
the parsing of escape sequences a little better.
SVN revision: 2168
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
Fixed a bug in the menu code reported by Sung-Hyun Nam
<namsh@lgic.co.kr>. There's also some new stuff here, but I haven't
tried testing it at *all*, so I'm not prepared to talk about it.
SVN revision: 2093
Fixed a bug with background colors and proportional fonts. Also added
an escape sequence, \e]30;<filename>\a, to dump the scrollback buffer
to a file. You will not get colors, or bold, or underlining, or any
other rendering information. Just the text. Linebreaks will appear
as they do on the screen.
SVN revision: 2090
The buttonbar can now be toggled on and off both in the config file
and via an escape sequence. The themes in CVS use Ctrl-Shift-Button3.
You can also specify in the config file whether to dock the buttonbar
at the top or the bottom of the Eterm window. You can't move it on
the fly yet, but that will come.
I also fixed resizing so that the term window didn't redraw itself
unnecessarily. Hopefully I didn't break anything in the process. :-)
Plus, I fixed poor handling of X-generated ConfigureNotify events, and
the terminfo stuff is now done at install time instead of build time.
SVN revision: 2077
This is the first public availability of the work thus far on Eterm
0.9.1. There's quite a bit of new stuff here.
* Added scrollbar thumb support.
* Completely redid the terminfo/termcap stuff. The terminfo file is
now compiled (by tic) and installed by default (unless you specify
--without-terminfo). The config files still say xterm, though,
because some programs (like SLang and GNU mc) use the silly algorithm
of "Is $TERM set to xterm?" to detect mouse reporting support in a
terminal. =P But if you don't ever use xterm, you can use Eterm's
termcap and just name it "xterm" instead. Thanks to Marius Gedminas
<mgedmin@takas.lt> for his patch that started this whole revamp.
* Added the kEsetroot script for KDE users from Dax Games
<dgames@isoc.net>.
* You can now configure the Home and End emulation via --with-home=
and --with-end= options to configure. The --with-terminfo option is
also new, and --enable-xim is now the default.
* Added a new image state, disabled, for when Eterm loses focus. This
is supported by all widgets (well, all those that could possibly be
on screen when Eterm lost focus), even the background image. So you
could actually have all your images darken on focus out and restore
to normal on focus in.
* Widget colors formerly dealt with as colors (menu text color,
scrollbar color, etc.) are now handled by the imageclasses. Each
image state can have a foreground and background color defined. The
current exception is the background image; I hope to add that later.
The foreground is the text color and the background is the object
color (for solid color mode). So menu text color is set by the menu
imageclass. And again, for unfocused colors, use the disabled state
of the imageclass.
* Proportionally-spaced fonts are now handled much better. They are
still forced into evenly-spaced columns (it's a terminal for crying
out loud!) but at least you don't end up with Eterm's wider than your
screen. :-)
* Home on refresh is gone, as is home on echo. It's now much simpler.
There are two options: home on output, and home on input, the former
being a combination of echo and refresh. Also, keypresses that don't
necessarily have corresonding output can trigger a home on input,
like Ctrl-End or whatever...ones that don't have special meaning.
Credit to Darren Stuart Embry <dse@louisville.edu> for pointing out
this issue and the one with "m-" in font names.
* I finally got around to re-merging the new parser stuff from my
work on the Not Game. Closed up some old potential behavior quirks
with theme parsing.
* Added a new escape sequence to fork-and-exec a program. Also added
a scrollback search capability to highlight all occurances of a string
in your scrollback buffer. Use the new "Etsearch" utility to access
it. "Etsearch string" to search for a string, then "Etsearch" by
itself to reset the highlighting.
* And of course, the biggie. Eterm now supports a completely-
customizeable buttonbar. Not a menubar, a buttonbar. It can have an
arbitrary number of buttons, and each button can perform an action,
just like a menuitem. So a button could bring up a menu (like a
menubar) or launch a program (like a launchbar) or perform an
operation (like a toolbar). Each button can have an icon, text, or
both. And you can have buttons left- or right-justified in the
buttonbar. You will eventually be able to have an arbitrary number
of buttonbars, but I'm still working on that.
As with any change this big, things could very easily be broken. So
beware. :-) I have tested this myself, and everything seems to work,
but I can't test every possibility. Let me know if you find anything
that's broken, and enjoy!
SVN revision: 2048
Updated the menu files to include all the new images in the background
collection. Also fixed a bug with solid-color menus and menus where
the selected state was not defined.
SVN revision: 1949
Fixed a minor emulation problem pertaining to the down arrow on the
keypad thanks to a patch from Marius Gedminas <mgedmin@takas.lt>.
SVN revision: 1918
More fixes with menus and transparency. After you build this version,
check out the brand new "glass" theme at http://www.eterm.org/. It
looks sweet. :-)
SVN revision: 1905
First commit of the new year! (Notice I didn't say the new millenium,
since *that* doesn't start until Jan 1, 2001.)
This should hopefully fix the bug where dead keys would bring up the
menu.
SVN revision: 1823
Finally fixed the seg fault pointed out by Tom Gilbert
<gilbertt@tomgilbert.freeserve.co.uk> back in mid-September where
small Eterms with little or no scrollback would crash when receiving
large amounts of data all at once.
I also fixed a clearing issue with double buffering, and I worked
around a really lame gdb/glibc2 bug that has prevented me from using
gdb with Eterm for ages.
SVN revision: 1804
I think I've finally got the menu behavior working right. Menus now
move themselves if needed, and exposes are now handled properly.
SVN revision: 1782
llane
Michael Jennings