Although I have yet to be able to reproduce it, I believe this will
fix Debian bug #104393. I don't think the lower parts of that array
were getting properly zeroed. :(
SVN revision: 4975
All the docs and themes should now be up-to-date. Unless a
showstopping bug turns up in the near future, this is pretty much it
for 0.9.1. Now we just need some testing to make sure there's
nothing horridly wrong.... So you all can test while we finish up
the web site and the backgrounds. :-)
SVN revision: 4919
This takes care of Debian bug #101777. Somebody was bitching that the
0-15 colors could no longer be used as values for the -f/-b/-c/etc.
options. I don't remember that ever being a feature to begin with,
but it took me all of 5 minutes to make it happen, so I figure what
the hell. Here ya go.
SVN revision: 4858
Several changes here, many of which come from the Debian bug list or
from bug reports on IRC. First off, I believe I've fixed an install
issue with the bg/ directory. I also put an alternative acsc line in
the terminfo file to see if it fixes anything on Debian. (RH works
fine.) I removed the "main" context from all the theme files...which
is something I should've done ages ago, but I forgot.
I made a couple things options which were not previously configurable.
The proportional font thingie which shrank the character cell width is
now the --proportional option. The automatic window gravity on resize
is now the --resize-gravity option. Both are boolean, and both are
documented in the man page.
And finally, I added the kill() function to the script language. At
this point it can only take signals as numbers, but that's good enough
for now.
SVN revision: 4857
Added a -a/--attribute option for passing config file stuff to the
parser on the command line. Also got the command line option section
of the man page up to date. I'll tackle the rest some other time;
it's late. :-)
SVN revision: 4820
There is now a new mechanism for dealing with the background image
collection, including a new update script. Please read the newly-
rewritten bg/README.backgrounds for details.
Also, I'm trying to flesh out the Contributors list in that file, but
my memory isn't cooperating. So if you contributed one of the
backgrounds, or know someone who did, please let me know.
SVN revision: 4810
Okay, first off, I removed 3 scaled backgrounds. See www.kainx.org or
my post to enlightenment-devel for details.
Second, I redid the default bindings for the mouse wheel. Basically,
the wheel alone will scroll by pages. Ctrl+wheel will scroll by pages
in groups of 5. Shift+wheel will scroll by a single line. If you
hold down the Alt key, the same combinations will work the same way,
but instead of scrolling within Eterm, they'll scroll the application
in the terminal (by sending PgUp/PgDn and up/down arrows). This works
in less, bash, and any other application which groks those keys.
I also added a --without-mousewheel option to configure that will turn
off the default scrollwheel bindings. Of course, you can always use
action bindings in the config file to bind/rebind these any way you
like.
While I was at it, I found and fixed a bug in the handling of the
Alt and Meta keys.
I added a scroll() function to the script stuff which allows you to
bind keys/buttons to scroll up and down. While I was at it, I added
comments to script.c for each function you can use.
And finally, the config file parser was moved to libast.
SVN revision: 4806
Finally got the selection stuff cleaned up. Hopefully this will be
the last time I have to deal with it for awhile. While I was at it,
I implemented incremental selection transfers. Unfortunately, it
doesn't seem like too many people support it. kedit doesn't, and it's
broken in Emacs (*grumble*). Works in gvim though.
SVN revision: 4784
I made several corrections to the terminfo entry noted by Thomas
Dickey <dickey@herndon4.his.com>:
- Removed cvvis. It wasn't actually supported and thus conflicted
with cnorm.
- Removed kf0, which conflicted with kf10.
- Added the CPR (u6) capability which I inadvertantly omitted.
I also removed the extraneous identities, keeping only "Eterm" and
"Eterm-color".
In a similar vein, I enabled the u8/u9 handshake while keeping the
ENQ (^E) response disabled.
SVN revision: 4773
Fixed the handling of menus larger than the screen, an issue noted by
Laurence J. Lane <ljlane@debian.org>. While I was at it, I also made
the pointer move along with the menu when a move is necessary.
SVN revision: 4752
Fixed several bugs in the saving of settings and the support of
scripts in menus. Also fixed the definition of term_name in the theme
files as pointed out by Laurence J. Lane <ljlane@debian.org>.
SVN revision: 4750
You can now create key, mouse button, menu item, and buttonbar button
bindings which trigger the parsing of a "script." I've thrown in a
few functions already to replace some icky escape sequences; there
will be many more functions forthcoming, although I don't know how
many of them (if any) will make it in prior to release.
The usage is pretty simple. Where before you might've said:
action string "\e]6;70\a"
you would now say:
action script "exit();"
You can call as many functions as you like per script. Use a
semi-colon (';') to separate each function call. If you only call
one function, the ';' is optional. If you aren't passing parameters
to the function, the parentheses are also optional. Parameters are
separated by commas and/or whitespace.
Valid functions currently are:
die(): die() is a synonym for exit().
exec(): exec() is a synonym for spawn().
exit(): Exit Eterm. Takes an optional exit code or message.
quit(): quit() is a synonym for exit().
save(): Save the config. Specify "theme" to save the theme
config. Also takes an optional path & filename.
search(): Search the scrollback buffer for a string.
spawn(): Spawns a sub-program. Defaults to "Eterm".
You will need the libast dated today to build and run this Eterm.
You will also need to update your themes.
SVN revision: 4748
Jeff Blank <jfb@mr-happy.com> pointed out that Sun's Workshop Pro
compiler defines __SVR4 but not __svr4__ or SVR4. This has now been
accounted for.
SVN revision: 4162
Added a spec file for Linux-Mandrake which was contributed (ages ago)
by Joakim Bodin <bodin@dreamhosted.com>. I don't plan on maintaining
this, so I hope he does. :-)
Also applied a menu change which I am hoping will fix an infinite
recursion bug in the menu system pointed out on SourceForge by
Jonathan S. Keim <jonkeim@princeton.edu>.
SVN revision: 4108
Applied a couple patches I'd overlooked in my inbox. Sebastian
Dransfeld <sebastid@stud.ntnu.no> added a config file option to
duplicate the behavior of the --buttonbar command-line option. He
also updated the man page, something I usually put off until just
before I do a release. :-)
I also went back and redid the way Eterm does backquote execution to
avoid a potential race condition.
SVN revision: 4083
Moved the HAVE_SAVED_UIDS define into a configure option so that the
FreeBSD folks will have an easier time with it.
Fixed "make distcheck" which broke at some point.
That X stuff in clean_exit() should only happen if we're debugging.
Nobody but me should have to deal with those random hangs. :-)
Added a patch for multibyte cursor support from Michael C. Wu
<keichii@iteration.net> and Sung-Hyun Nam <namsh@lgic.co.kr>, along
with some other FreeBSD-related patches from Mr. Wu.
SVN revision: 4065
At the request of Snow-Man <sfrost@snowman.net>, I added the build
date to the output of --version. While I was at it, I also added the
RCS ident strings.
I also applied a patch from Sung-Hyun Nam <namsh@lgic.co.kr> that
fixes XIM-related seg faults during clean-up.
SVN revision: 3919
VA bought some licenses for Insure++, so I've been using it to audit
Eterm. These are just the initial results of the collaboration; there
will most likely be more. So far things are looking pretty good. I
just wish Insure++ had more helpful messages. I'd really love to be
able to track down those reads/writes involving freed pointers that
it claims to have found in Imlib2....
I also had to try and make the build work without MMX. I did so; I
just hope it still works *with* MMX.... =)
SVN revision: 3895
As requested by Chris Morton <chris.morton@ericsson.com>, I added
support for the SunCut, SunCopy, SunPaste, and SunFront keys. The 1st
3 operate on the xclipboard-managed "ClipBoard" buffer. The SunFront
key will activate Eterm's "steal focus" mechanism.
SVN revision: 3891
Since someone wanted it, if no name is given but an exec line (the -e
option) is given, the name defaults to the first word in the exec line
instead of "Eterm-<version>". For example, Eterm -e ssh foo would get
the title "ssh". NOTE: Most Eterm themes already specify a name, so
this will not work with those themes.
SVN revision: 3886
Thanks to continuing help from Sung-Hyun Nam <namsh@lgic.co.kr>, I
finally figured out the double-buffering problem people were seeing.
And as it turns out, his original patch was correct. So now it's
fixed. Many thanks for his assistance.
SVN revision: 3847
Fixed the error message bug I noticed. There's also a big5 fix from
Chung-Yen Chang <candyz@cle.linux.org.tw>, and I got rid of some
tiny memory leaks in the X data, the first of which was noticed by
zed@linuxpower.org.
SVN revision: 3844
bigfont/smallfont keys to change between two fonts of the same size (sabvga
and ansi for example), the screen wasn't redrawn to reflect the new font.
Now it is, and I hope I did it right or KainX will destroy me :-)
SVN revision: 3830
Several small changes, like freeing pixmaps which won't be needed
later, reducing the default Imlib2 cache size to 0 bytes (we don't
really use it well), and an image path bugfix spotted by Teodor
Zlatanov <tzz@iglou.com>.
The big change, of course, is the disappearance of libmej and the new
dependency on libast, which is now distributed separately.
SVN revision: 3793
When shaded, rely on Enlightenment rather than X for accurate x/y
position information. This fixes a bug pointed out by Gnea
<gnea@rochester.rr.com>.
SVN revision: 3509
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
Okay, everything seems hunky-dorey now. If you have memory debugging
turned on, exiting Eterm will give a dump of the leftover allocated
memory including where it came from and how much there is. You'll
also get a listing of all the remaining Pixmap ID's and GC ID's along
with where they were created.
I also added some macros to the debugging stuff in libmej.h so that
if you pass the --without-debugging option to ./configure, it will
optimize out all the ASSERT and REQUIRE goop. This will make it
harder to trap bugs before they cause problems, so don't do it if you
want to help development, but if speed is critical to you, give it a
shot.
SVN revision: 3294
That should fix the crashes. Somehow I managed to temporarily forget
about pointer arithmetic. And somehow I thought trying to dereference
a pixmap ID would be a good thing. Sigh. I need sleep.
SVN revision: 3292
Massive reorganization/rewrite to libmej. It should now be 100%
independent of Eterm. There still may be some gremlins in the memory
debugging code, so don't use too high a number with --debug....
SVN revision: 3282
Color modifiers for images now work once again. Please report any
problems you find with them as soon as possible; I want to get 0.9.1
out the door in the fairly near future since the TODO list for 0.9.2
is already sizeable.
SVN revision: 3241
Two more patches from Marius Gedminas <mgedmin@takas.lt>. The first
one allows for customization of the message displayed when Eterm goes
into pause mode. There are actually two; one goes in the titlebar,
and the other is displayed in the text window.
His second patch makes Eterm's behavior a little smarter when it
resizes itself. It tries to figure out which quadrant of the screen
it's on and resizes in the most appropriate direction. (For example,
Ctrl-GreaterThan on an Eterm in the lower right corner will cause the
upper left corner of the Eterm to move; the lower right corner will
stay put.)
Thanks again to Marius for saving me time by sending patches. :-)
SVN revision: 2912
I think I've finally fixed all those XPolyText8() errors with pixmap
support disabled. Solid color mode buttonbars seem to work now also.
SVN revision: 2907
The multibyte font size patches caused weird behavior if your
multibyte font sizes didn't match your regular font sizes for those
who don't actually use the multibyte support. So I fixed that. I
also fixed the XA_TEXT problem for people using old/broken X.
SVN revision: 2904
Several people have asked for the spec file to be in the tarball so
that rpm -ta <tarball> works properly. I've put it in there, but I
don't recommend doing it that way. I use /usr/local as my prefix, and
there's a good chance I'll forget to change it before doing a dist
tarball.
I also put some dummy crap in pixmap.h so that compiling without
Imlib2.h works again.
SVN revision: 2903
I think this --pause mechanism will be agreeable to everyone. You can
once again exit with any key (well, any key that has an actual
character/string associated with it by X...not Insert, Home, etc.),
but keys Eterm uses (like Shift-PgUp) will still work as expected.
SVN revision: 2902
Marius Gedminas <mgedmin@takas.lt> reported a couple of issues back
when he was on his bug-spotting binge that I didn't have time to fix
just then. Well, now I've fixed them. ~/.Eterm/user.cfg will now
be found if there isn't a theme-specific one; this allows you to have
a single user.cfg which specifies some options you want all your
Eterms to have.
Along those same lines, the action code now searches for duplicate
bindings and changes the existing one rather than adding a new one
to the end of the list. This allows bindings in user.cfg to override
those in theme.cfg (as they should). Also, bindings are added in
reverse order, so newer ones (like in user.cfg) take precedence over
older ones (like in theme.cfg) if there is a conflict (e.g., if your
theme.cfg binds "anymod button2" and user.cfg binds "ctrl button2,"
user.cfg wins).
SVN revision: 2901
Oops! The font size patch from the other day broke without multibyte
font support enabled, which meant the XFree86 3.3.x people were
screwed. Fixed now.
SVN revision: 2893
Patch from Sung-Hyun Nam <namsh@lgic.co.kr> to fix multi-byte font
handling when the ISO-8859 font size doesn't match the multi-byte font
size.
SVN revision: 2846
Fixed an old rxvt bug in the handling of "\e[0m". I *really* wish I
had time to rewrite that damned thing. Such a piece of crap. Thanks
again to Marius Gedminas <mgedmin@takas.lt> for pointing it out.
SVN revision: 2780
Fixed a seg fault when resizing to one row while on the secondary
screen. I have no clue how that bug crept in there all of a sudden,
but thanks to Marius Gedminas <mgedmin@takas.lt> for pointing it out.
SVN revision: 2772
Dammit! I did something really stupid. For anyone who doesn't know
already, calling X from a signal handler is a NO-NO. The *really*
stupid part is that I already KNEW that! *slaps self*
SVN revision: 2745
Okay, first off I need to thank Marius Gedminas <mgedmin@takas.lt>.
Not only did he point out several issues, he was even willing to send
a patch. :-)
This commit includes Marius' patch which keeps MappingNotify events
from overriding users' modifier settings. It also includes a fix to
a seg fault that he pointed out when menus were loaded without the
menu imageclass having been defined.
He also pointed out that --pause tends to sit and spin, taking up 100%
of the CPU time. Funny how E-Cpu never seemed to get too bent out of
shape over it, but he was indeed correct.
Thus I have fixed it, and while doing so, I have changed the way it
works. It no longer waits for a keypress per se. Actually, it just
ignores the fact that its child went away and keeps right on taking
X events. There are a few exceptions though. Either ESC or Ctrl-C
will exit a paused Eterm. Any other input that doesn't have special
meaning to Eterm will be ignored. (Shift-PgUp and Shift-PgDn still
work however, as do any action bindings you may have.)
SVN revision: 2739
My attempt to track down the strange X errors have revealed that a
pixmap given to me by Imlib2 is getting freed somehow behind my back.
Probably because this part of Imlib2 hadn't been tested before Eterm
was converted. =P
It doesn't seem to happen in XFree86 4.0; I'm wondering if XFree 4 is
smart enough to detect double-frees of old XID's and just ignore them?
Well, I'm going to have to add some debugging code to Imlib2 and see
if I can track down where it's freeing my pixmaps. But I have some
errands to run first, so I'm going to commit this for now. It
shouldn't actually change any functionality.
SVN revision: 2722
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
Added new shade/tint routines, including some done in MMX assembly, by
Willem Monsuwe <willem@stack.nl>. Thanks Willem! These should prove
to be faster than the old stuff, probably by quite a bit.
SVN revision: 2595
Fixed a bug in the handling of resize events thanks to a tip from
Teodor Zlatanov <tzz@iglou.com>. While I was at it, I also fixed a
couple remaining issues with the popup menu system. You shouldn't
get any more cases where items remain selected after you've moved your
mouse off of the menu, or where a submenu would stay up even though
another menuitem is selected.
SVN revision: 2594
After getting sick of hearing people whining about the obscure error
messages that resulted from trying to build without pixmap support, I
hacked it until it at least built without it. I also added warnings
to configure.in so that people would know if that happened.
It's still not very happy running that way, which is something I need
to fix. But hopefully it will stop the whining.
Yeah, right. =P
SVN revision: 2590
Added the pixmap beveling support back in so that the glass theme will
work again. Once again, you poor 8 bpp saps are SOL.
I also added the icon support back in, along with a new built-in icon
courtesy of Brian McFee <keebler@sandwich.net>.
SVN revision: 2501
I fixed the problem reported by Joakim Bodin <bodin@dreamhosted.com>
with spawned processes. Also fixed Esetroot as reported by Wayne
Johnson <bigman1@alltel.net>.
Support for buttons higher than 5 was also added to the action
bindings code for those (like me) with IntelliMouse Explorers and
XFree86 4.0. :-)
SVN revision: 2494
This is the initial commit with Imlib2 support. READ THIS CAREFULLY.
There is important information in this commit message that will keep
you from getting screwed.
First off, support for Imlib 1.x is GONE. It is no longer supported
as of now. If you want to continue using it, do NOT install this
version. I tried to support both for awhile, but the code ended up
being way too ugly and hackish. Imlib2 is the future. And trust me,
when you see what we do with this future, you'll be happy for the
switch.
The good news is that most of the basics work. Transparency still
works, and the basic image stuff works. Most users won't notice any
major problems, so long as your Imlib2 is 100% up-to-date.
However, a few things still don't work:
1. Auto mode is a bit broken. You'll get X errors in XFree86 4.0.
Don't use it if you're running XFree 4.
2. Color modifiers for images don't work. At all.
3. Transparency shading/tinting will not work in 8bpp or lower. Life
blows sometimes. Sorry. Time for a real video card. :-)
4. The built-in icon is broken.
5. You WILL need to update your theme.cfg files. The borders on the
horizontal and vertical bar images were incorrect when combined with
the new anti-aliased scaling. The horizontal bars should have a right
border of 3. Vertical bars should have a bottom border of 3. The
menu images should have both right *and* bottom borders of 3. You can
either make those changes by hand, or use the --with-theme-update
option to autogen.sh. Your call.
I think that covers everything I've run into. I will point out that
I don't really take advantage of a lot of the Imlib2 features just
yet. My first priority is to make all the stuff that worked before
work again (or at least the important stuff). Then I'll work on
new features.
So there it is. If you're not ready for it, don't use it. But if you
are, I hope you like it.
SVN revision: 2478
There are now two different sets of settings you can save. You can
save user settings, which are the things that one would generally
consider to be user-specific (toggles, text colors, etc.). You can
also save theme settings, which saves *everything*, including the
stuff that user settings don't include (like imageclasses, menus,
etc.). Settings are saved to user.cfg and theme.cfg, respectively.
Also, Eterm will now detect if it cannot write to the location from
which it got the theme (i.e., a system-wide directory), and will fall
back on ~/.Eterm/themes/<theme>. It WILL create this directory tree
if it does not already exist.
Hopefully this will make more people happy. :-)
SVN revision: 2440
Quick little option -q/--no-input. It keeps Eterm from accepting
keyboard input, and keeps the window manager from focusing it. Useful
for log tailers and such, maybe. This feature was requested by
Peter Ward <than@ilm.com>. I will be adding an escape sequence to
toggle this.
SVN revision: 2398
Tint by number or color, and shade by percentage, are now available
via the "\e]6;2;" escape sequence. For example, "\e]6;2;shade;10\a"
will shade the background by 10%. "\e]6;2;tint;lightblue\a" will give
the background a light blue tint. "\e]6;2;shade;sa;30\a" will give a
30% shade to the scrollbar anchor.
SVN revision: 2370
Added a patch from Kimball Thurston <kimball@sgrail.com> for XIM. I
also added support for two new escape sequences at the request of
Cale Gibbard <gibbard@bfree.on.ca>. "\e]Pnrrggbb" can now be used
to modify the color palette at runtime, and "\e]R" will restore the
defaults. These are compatible with the Linux console.
SVN revision: 2323
I added accelerated scrollwheel support. I also added a #define in
src/feature.h for specifying the number of lines of context to keep
when paging up or down.
Also, we're back to the old behavior where home on input won't be
triggered unless the key pressed has an associated string value. I
went back on this because Shift causing a jump to the bottom was
really annoying when trying to Shift-PgUp or Shift-PgDown. Sorry,
Darren, but you lose.
SVN revision: 2270
Some further fixes for inline functions, 2 new winop actions, brand
new and improved profiling macros, some miscellaneous fixes for SGI
from Kimball Thurston <kimball@sgrail.com>, and more robust checking
in the pasting code.
SVN revision: 2235
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
I fixed a bunch of double-buffering stuff here. I'm going to use it
by default on my own Eterms for awhile, and if I don't hit any snags,
I'll make it the default in the themes.
SVN revision: 1708
Oops. I intended to test without multi-charset before committing, but
I seem to have forgotten to do that. Lots and lots of people
submitted various patches for this, but I didn't use any of them. But
thanks to all for pointing out my error. :-)
SVN revision: 1603
I finally got around to implementing double-buffering, although it
seems to still have some issues with font changes. But if you don't
change fonts, it works great. :-)
I also fixed the multibyte font stuff with help from Sung-Hyun Nam
<namsh@lgic.co.kr>. There seem to be some new issues here, though,
with the background pixmap. But I'm to tired to look deeper tonight.
SVN revision: 1588
Support for RedHat's utempter library and some other fixes. Thanks to
Erik Troan <ewt@redhat.com> and Tim Powers <timp@redhat.com> for their
help with this.
SVN revision: 1547
A good number of changes here. First off, since nobody reported any
bugs with the new font stuff, I switched the multibyte fonts over to
use it as well. They do use the same font index, however, in order to
keep the sizes matched up.
I also fixed up the modifier stuff so that Meta and Alt are matched
by KeySym rather than assuming Mod1. I also took care of the action
dispatcher so it would keep up with these changes.
To go along with this, I added 3 new options and config file
attributes which allow you to set the modifier that should represent
Meta, Alt, and NumLock. This overrides the automatically-detected
X server settings.
I also applied some fixes to the XIM code from Sung-Hyun Nam
<namsh@lgic.co.kr>.
SVN revision: 1482
Once again, I've rendered old themes obselete. :-)
I added a new config file attribute and command-line parameter. The
option is --default-font-index, but I wouldn't necessarily use it.
The config file attribute makes more sense. :-)
Anyway, your themes will now need to have a line like this:
font default <index>
in the attributes section. This tells Eterm which font it should use
on startup. (<index> is a number between 0 and the highest-numbered
font you define.) You can now have up to 256 fonts. Font 0 is no
longer necessarily the default font; it is the smallest font. And the
larger the font index, the larger the font should be. (Of course,
this assumes you want Ctrl-> and Ctrl-< to increase/decrease your font
size. In reality, you can have your fonts in any order, and those
keys will cycle through them in order.)
Before, font 0 was always the default, and you didn't have much
freedom in rearranging your fonts. Plus, you were limited to 5. Not
any more. :-) The new system is much more straight-forward, logical,
and powerful.
So please be sure to update your themes by hand, or remove your theme
directory before installing this new version. If your theme lacks
the "font default" line, your Eterms will start with the wrong font.
:-]
SVN revision: 1344
Okay, I think I have everything back in working order. PLEASE test
this thoroughly, as an awful lot has changed. Let me know what I
broke. :)
SVN revision: 1339
I've rewritten almost the entire scrollbar. It mostly works, but it
still has issues. I've put an #error directive in so that it won't
compile; take it out if you *really* wanna try it. It's much more
efficient than before.
SVN revision: 1333
Some selection changes and escape sequence fixes. You can now
specify multiple color modifier commands in a single escape sequence.
You can also remove any existing color modifiers using "clear".
SVN revision: 1324
Two more bugs fixed. One, Trevor Powell <vulpine@zikzak.net> spotted
an issue with left-side scrollbars which is now fixed. Two...um...
ahem. Fixed the auto mode titlebar thing. *cough* Turns out I was
doing something stupid with my IPC window (i.e., not having one) that
caused E to ignore lots of events on my window. Oops, sorry folks.
raster has given me the cl00bat beating, so it's fixed now. :-]
SVN revision: 1314
Okay, I've fixed a lot here. First off, I fixed the bug Gnea
<gnea@rochester.rr.com> pointed out with toggling Max Size in E.
Turned out to be a symptom of a much larger problem, but it should be
fixed now. Then I corrected the XIM issues pointed out by Sung-Hyun
Nam <namsh@lgic.co.kr> and Jerome De Greef
<jerome_degreef@hotmail.com>, as well as a stupid typo on my part that
Jerome happened upon. Next I fixed the bug Adam Lucas
<ALucas@wcom.net> spotted with changing the scrollbar type. While
fixing that, I also fixed changing the scrollbar width. Both
operations are a lot smoother and cleaner now.
SVN revision: 1292
All the settings should save now, so if something doesn't work or I
missed something, report it as a bug.
HOWEVER! Keep in mind that "Save Settings..." saves to a file called
user.cfg in the current theme directory. This means two things. One,
if you do not have write permissions to the current theme directory
($ETERM_THEME_ROOT), it will fail. Two, if you save settings to the
default (Eterm) theme, these settings will override ALL your other
themes! If you save settings to the default theme, you better expect
to get those settings everywhere, unless the other themes also contain
user.cfg files.
SVN revision: 1214
Several bugs fixed here, most notably a potential seg fault in
Esetroot, and remembering an Eterm's size works again. Also a minor
redraw speedup. And %exec() now works properly instead of just
causing Eterm to crash. :-)
SVN revision: 1153
You can now apply additional color modifiers to the various widgets
in transparent mode that further modify the background. So, in other
words, you could have a scrollbar anchor that, in the normal state,
is darker than the transparent background, and in selected/clicked
state, is brighter. Or any variation on that theme. :-)
Once you've got this version going, try the following changes to your
trans theme's config file:
begin image
type anchor
mode trans allow image trans auto
state normal
file bar_vertical_1.png
geom :scale
border 3 3 2 2
cmod image 192
bevel up 1 1 1 1
state selected
file bar_vertical_2.png
geom :scale
border 3 3 2 2
cmod image 320
bevel up 1 1 1 1
end image
You'll see what I'm talking about. :-)
SVN revision: 1043
Fixed a couple problems pointed out by Joel Lesher
<filgy@blazenet.net> and Rahsheen Porter <strider@cipher.neuplanet.cx>
regarding tinted/shaded transparency and a typo in the auto mode
theme file. Doh!
SVN revision: 1038
Nothing really important here. I may have fixed the refresh problem
that a lot of people see when switching desktops and IRC-ing in an
Eterm, but I'm not sure. And I have once again discovered (well,
re-discovered actually) that the remaining bits of rxvt code in the
scrollbar are smelly piles of poop that I really need to get around
to fixing one of these days.
SVN revision: 1032
I fixed the popup scrollbar bug with transparency, but I fixed lots
more than that. I removed a lot of duplicate event handling, lots of
duplicate redraws, and lots of unnecessary transparency updates. In
doing so, I fixed the latency problem people had been reporting with
several shaded/tinted transparent Eterms while changing desktops. I
also threw solid color transparency support in the mix while I was at
it. All in all, you should notice significant speedups in transparent
Eterms.
SVN revision: 1031
Fixed lots of issues revealed by the -ansi -pedantic flags. The only
warnings you get with those flags now are implicit declaration
warnings for non-ANSI functions and warnings specific to certain OS's
and their non-ANSI implementations of ANSI functions, neither of
which I can do much about. :-)
SVN revision: 1010
This should get rid of all the warnings. If you're running Linux and
get warnings about setresuid, setresgid, grantpt, and unlockpt not
having prototypes, feel free to add the following lines to your copy
of /usr/include/unistd.h:
/* Linux- and HP-UX-only setres?id() calls -- mej */
extern int setresuid(uid_t ruid, uid_t euid, uid_t suid);
extern int setresgid(gid_t rgid, gid_t egid, gid_t sgid);
/* SVR4 PTY functions */
extern int grantpt(int fd);
extern int unlockpt(int fd);
SVN revision: 886
Almost all the warnings are gone. only 3 remain on my system at home.
two in command.c (where do I get proper prototypes for grantpt() and
unlockpt()?) and one in options.c that is bizarre:
options.c:3433: warning: `%x' yields only last 2 digits of year in some
locales
SVN revision: 871
Warnings begone!
Eterm/src/command.c still has two warnings but I don't know why
I didn't get rid fo them. there are still warnings in
Esetroot.c and in Etbg, but I'll fix those later.
SVN revision: 866
Lots of cleanups here, including a couple fixes for bugs noticed by
Tom Gilbert <gilbertt@tomgilbert.freeserve.co.uk> and Martin Tyler
<martin@boo.org>. Also removed the requirement of glibc 2.1 for using
SVR4-style pty's (/dev/pts/*) under Linux.
SVN revision: 798
Shaved off around 100 KB of memory usage per Eterm by moving more
code into the shared library, removing lots of unneeded variables, and
fixing some small leaks here and there.
SVN revision: 710
Auto mode has been fixed to work with the newest E. If you don't have
the newest E, it won't work. So don't bug me about it; just upgrade.
Your version of E must be dated October 7th or later, or all bets are
off.
I also cleaned up some stuff to save lots of unnecessary redraws and
(if you're in auto mode) E IPC transactions.
A bug in the value set for $IFS was also fixed. Thanks to Kimball
Thurston <kimball@sgrail.com> for pointing out my oversight.
Furthermore, I added a parameter to the --enable-multi-charset option
for configure. You can now specify =utf-8 to get UTF-8 fonts for the
multi-byte mode stuff. If you pass =kanji (or no value at all), you
will still get the old Kanji fonts. If you use multi-byte Eterm and
have a set of fonts for other setups (Big 5, Cyrillic, etc.), please
let me know and I'll add a parameter for those too.
SVN revision: 706
Michael Jennings
Tom Gilbert
Mandrake