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
Michael Jennings
Mandrake