Reverted part of a patch from Chris Schoeneman <crs23@bigfoot.com>
(changelog entry "Fri Jun 25 17:48:24 2004") which broke dead keys and
compose-key sequences.
Fixed autoSHIT for dist/distcheck/distclean/maintainer-clean and newer
autoSHIT versions.
Fixed error in saving of cut_chars attribute.
Fixed saving/handling of beep_command attribute.
----------------------------------------------------------------------
SVN revision: 13745
Merged in previous autoFUCK changes from libast.
Added a feature to specify a command to be run in place of the normal
PC speaker beep.
----------------------------------------------------------------------
SVN revision: 13484
Okay, so my first problem was that I didn't pay close enough attention
to the iconv_open() man page and got the parameter order wrong. Duh.
Thanks to Sytse Wielinga <s.b.wielinga@student.utwente.nl> for
noticing that.
kwo suggested using XmbDrawString(), but that causes font problems I'm
not ready to diagnose just yet.
----------------------------------------------------------------------
SVN revision: 12526
Another attempt (and failure) at UTF-8 support. Disabled until
someone can help me out.
If you know iconv(), please have a look at the FIXME_BLOCK starting at
line 3509 of src/command.c.
----------------------------------------------------------------------
SVN revision: 12495
The benefits of being a passenger on a long road trip... The
beginnings of EWMH opacity (a la xcompmgr) support and (hopefully)
UTF-8 support. Both as yet untested.
----------------------------------------------------------------------
SVN revision: 12471
Small patch for building against libast 0.6.1.
Fixed compile error when enabling OFFIX_DND support pointed out by JG
Miller <miller@yoyo.org>.
----------------------------------------------------------------------
SVN revision: 12140
Kirby Kuehl <vacuum@technotronic.com> pointed out some portability
issues. These should now be fixed.
----------------------------------------------------------------------
SVN revision: 10983
If $LANG refers to a UTF-8 or similar locale, remove that part. In
other words, en_US.utf8 becomes en_US instead.
----------------------------------------------------------------------
SVN revision: 10868
Applied patch from Kim Woelders <kim@woelders.dk> to fix setting of
_NET_WM_ICON property.
Fixed a couple warnings.
----------------------------------------------------------------------
SVN revision: 10834
Chris Schoeneman <crs23@bigfoot.com> pointed out that Eterm didn't get
keypresses if another app (like synergy) decided to listen for its
events. This should correct that behavior.
----------------------------------------------------------------------
SVN revision: 10583
Enable title-reporting and iconname-reporting escape sequences only if
specifically requested by user at compile time. This exists solely to
protect the ignorant and careless from themselves.
SVN revision: 9812
As requested by Ben Armstrong <synrg@sanctuary.nslug.ns.ca>, saving
theme settings will not preserve -e/--exec arguments unless a theme
was specifically named by the user.
SVN revision: 9811
Fixed stupid mathematical blunder in the font handling code pointed
out by Laurence J. Lane <ljlane@debian.org>.
Allow save_buff() script function to dump to stderr if no file is
specified. Note that script functions CANNOT be triggered by escape
sequences.
SVN revision: 7818
Patch from David Lloyd <dmlloyd@tds.net>. Removed the NO_BRIGHTCOLOR
and NO_BOLDOVERSTRIKE defines. If you want to do NO_BRIGHTCOLOR, set
colors 8-16 the same as 0-7. :P For bold overstrike, it's now an
option (--overstrike-bold). There are also options to deactivate the
"bold" and "blink" attributes' setting of high-intensity colors, and
to allow non-default foreground colors to be bolded.
SVN revision: 7377
I redid the options variables and constants to try and make things
more standardized, and to make room for future toggles as well. This
should make David Lloyd a bit happier, 'cause now we can get his patch
in here. :)
Hopefully I didn't break anything....
SVN revision: 7370
Patch from David Lloyd <dmlloyd@tds.net> to support ANSI sequences for
bright colors. I haven't tested this, so I hope it works. *grin*
Also, commented out the F1-F10 bindings in the Escreen theme; they're
too intrusive.
Added support for Ctrl-t to open a new Escreen "tab" (as with
Mozilla).
SVN revision: 7261
Fixed seg fault caused by people who neglect to grow the multichar
font list in parallel with the normal font list.
Also tweaked the default fonts to be less error-prone.
SVN revision: 6878
Fixed a couple minor type issues on 64-bit systems.
Cleaned up all the warnings in libscream.c and Esetroot.c.
Updated the spec file to depend on imlib2 and the JPEG/PNG loaders.
I hate to do that, but it seems necessary.
SVN revision: 6874
Fixed a bug with foreground/background color change pointed out by
Thomas <arnognul@tiscali.se>.
Also added support for all the other OSC color change sequences (at
least those for the colors that Eterm uses). The sequences are of
the form "\e];n;color[;color[...]]\a", where n is between 10 and 19.
You can specify up to (20 - n) semicolon-separated colors representing
the following attributes in order: foreground, background, cursor,
mouse pointer, mouse pointer background (*), Tek foreground (*), Tek
background (*), highlight color (*), bold color, and underline color.
Attributes marked with a (*) are ignored by Eterm and may be left
empty, but their trailing semicolons must be present for xterm
compatibility.
For example, to set a white foreground, black background, yellow text
cursor, green mouse cursor, #ffaa00 for bold, and cyan for underline,
you could use either of the following:
echo -e "\e]10;white;black;yellow;green;;;;;#ffaa00;cyan\007"
or
echo -e "\e]10;white\007"
echo -e "\e]11;black\007"
echo -e "\e]12;yellow\007"
echo -e "\e]13;green\007"
echo -e "\e]18;#ffaa00\007"
echo -e "\e]19;cyan\007"
Note that the setting of bold and underline colors using 18 and 19 are
Eterm extensions.
SVN revision: 6739
Screw it. I don't see any way to "sanitize" these, as they put it,
so we'll just disable that for now until someone can throw me a clue.
SVN revision: 6715
This fixes the title answer bug reported on BUGTRAQ (and other lists)
by HD Moore <termulation@digitaloffense.net>. It does so by removing
all non-printable characters from the title upon setting it, and
blanking out all non-printable characters when fetching it to display
using the aforementioned escape sequence.
SVN revision: 6712
Patch from Paul Brannan <pbrannan@atdesk.com> to fix a conflict
between twin's non-standard mouse drag reporting and vim when twin
support is not enabled.
SVN revision: 6696
Michael Jennings
swielinga