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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Added support for xterm's property change escape sequence as requested
by Greg Badros <gjb@cs.washington.edu>, the originator of the
sequence.
SVN revision: 353
Lots of changes here. First off, this should fix the background draw
bug with transparency that several people pointed out. While I was
at it, I also cleaned up a lot of other related stuff. Three-state
images should be a lot more robust now.
Then again, some stuff may be broken entirely from this, so let me
know. :-)
For one thing, the various image modes should work as expected now.
You can allow and disallow modes for the various widgets. The
fallback mode is "solid" now, rather than "image," so you can cause
a certain widget to refuse to use an image if you want to. If you
specify an image without specifying a "mode" line that allows the
"image" mode, your image will not appear. <-- READ THIS TWICE! I
had to go back and fix all the theme files because of this, so you
will need to remove your current theme directory and allow Eterm's
"make install" to put the new ones in place; otherwise, everything
will go back to being solid colors. =]
Anytime something changes this drastically, there are bound to be
problems. Let me know if you find any of them. :)
SVN revision: 348
Lots of changes here. First off, this should fix the background draw
bug with transparency that several people pointed out. While I was
at it, I also cleaned up a lot of other related stuff. Three-state
images should be a lot more robust now.
Then again, some stuff may be broken entirely from this, so let me
know. :-)
For one thing, the various image modes should work as expected now.
You can allow and disallow modes for the various widgets. The
fallback mode is "solid" now, rather than "image," so you can cause
a certain widget to refuse to use an image if you want to. If you
specify an image without specifying a "mode" line that allows the
"image" mode, your image will not appear. <-- READ THIS TWICE! I
had to go back and fix all the theme files because of this, so you
will need to remove your current theme directory and allow Eterm's
"make install" to put the new ones in place; otherwise, everything
will go back to being solid colors. =]
Anytime something changes this drastically, there are bound to be
problems. Let me know if you find any of them. :)
SVN revision: 345
Worked around a XF86 3.9.16 (perhaps Xinerama) problem. Also added
some XIM changes from Sung-Hyun Nam <namsh@lgic.co.kr> to handle
buffer overflows.
SVN revision: 274
Patch from Sung-Hyun Nam <namsh@lgic.co.kr> for the theme files. Also
added a timeout for the backtrace attempt so that it hopefully won't
hang around forever when gdb decides to hang.
SVN revision: 204
Michael Jennings