1999-08-17 16:01:18 -07:00
|
|
|
dnl# $Id$
|
|
|
|
|
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_INIT(src/feature.h)
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
AM_INIT_AUTOMAKE(Eterm, 0.9.1)
|
1999-08-17 16:01:18 -07:00
|
|
|
|
|
|
|
|
dnl# Set some basic variables
|
1999-08-17 18:12:47 -07:00
|
|
|
DATE="`date '+%d %B %Y'`"
|
1999-08-17 16:01:18 -07:00
|
|
|
AC_SUBST(DATE)
|
2000-11-24 18:55:40 -08:00
|
|
|
BUILD_DATE="`date`"
|
|
|
|
|
AC_DEFINE_UNQUOTED(BUILD_DATE, "$BUILD_DATE")
|
2000-03-14 19:17:45 -08:00
|
|
|
AUTHORS="Michael Jennings (mej@eterm.org) "
|
1999-08-17 16:01:18 -07:00
|
|
|
AC_SUBST(AUTHORS)
|
1999-08-18 18:22:17 -07:00
|
|
|
AC_DEFINE_UNQUOTED(AUTHORS, "$AUTHORS")
|
1999-08-17 16:01:18 -07:00
|
|
|
|
2000-11-24 18:55:40 -08:00
|
|
|
dnl# Find RCS Ident info from source files
|
2000-12-29 14:59:13 -08:00
|
|
|
AC_DEFINE_UNQUOTED(ACTIONS_IDENT, "`grep '$''Id:' $srcdir/src/actions.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(BUTTONS_IDENT, "`grep '$''Id:' $srcdir/src/buttons.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(COMMAND_IDENT, "`grep '$''Id:' $srcdir/src/command.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(DRAW_IDENT, "`grep '$''Id:' $srcdir/src/draw.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(E_IDENT, "`grep '$''Id:' $srcdir/src/e.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(EVENTS_IDENT, "`grep '$''Id:' $srcdir/src/events.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(FONT_IDENT, "`grep '$''Id:' $srcdir/src/font.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(GRKELOT_IDENT, "`grep '$''Id:' $srcdir/src/grkelot.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(MAIN_IDENT, "`grep '$''Id:' $srcdir/src/main.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(MENUS_IDENT, "`grep '$''Id:' $srcdir/src/menus.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(MISC_IDENT, "`grep '$''Id:' $srcdir/src/misc.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(NETDISP_IDENT, "`grep '$''Id:' $srcdir/src/netdisp.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(OPTIONS_IDENT, "`grep '$''Id:' $srcdir/src/options.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(PIXMAP_IDENT, "`grep '$''Id:' $srcdir/src/pixmap.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(SCREEN_IDENT, "`grep '$''Id:' $srcdir/src/screen.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(SCROLLBAR_IDENT, "`grep '$''Id:' $srcdir/src/scrollbar.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(STARTUP_IDENT, "`grep '$''Id:' $srcdir/src/startup.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(SYSTEM_IDENT, "`grep '$''Id:' $srcdir/src/system.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(TERM_IDENT, "`grep '$''Id:' $srcdir/src/term.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(TIMER_IDENT, "`grep '$''Id:' $srcdir/src/timer.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(UTMP_IDENT, "`grep '$''Id:' $srcdir/src/utmp.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
|
|
|
|
AC_DEFINE_UNQUOTED(WINDOWS_IDENT, "`grep '$''Id:' $srcdir/src/windows.c | sed 's/^.*\$''Id: //;s/ \$.*$//;s/.v / /;s/ Exp//'`")
|
2000-11-24 18:55:40 -08:00
|
|
|
|
1999-08-17 16:01:18 -07:00
|
|
|
dnl# Supply default CFLAGS, if not specified by `CFLAGS=flags ./configure'
|
|
|
|
|
if test ! -z "${CFLAGS}" -o ! -z "${CCOPTS}"; then
|
|
|
|
|
CFLAGS_GIVEN=1
|
|
|
|
|
else
|
|
|
|
|
CFLAGS_GIVEN=0
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
if test -z "${CFLAGS}"; then
|
|
|
|
|
if test -z "${CCOPTS}"; then
|
|
|
|
|
CCOPTS="-O"
|
|
|
|
|
fi
|
|
|
|
|
CFLAGS="$CCOPTS"
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
AC_ARG_WITH(cc, [ --with-cc=compiler force Eterm to build with a particular compiler (like pgcc, egcs, etc.)],
|
|
|
|
|
CC=$withval,
|
|
|
|
|
if test -z "$CC"; then
|
|
|
|
|
CC=check
|
|
|
|
|
fi
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
if test "$CC" = "check"; then
|
2000-04-03 16:43:15 -07:00
|
|
|
dnl# Check for Pentium compiler
|
1999-08-17 16:01:18 -07:00
|
|
|
AC_CHECK_PROG(PGCC, pgcc, pgcc)
|
|
|
|
|
|
2000-04-03 16:43:15 -07:00
|
|
|
if test ! -z "$PGCC"; then
|
1999-08-17 16:01:18 -07:00
|
|
|
CC=$PGCC
|
|
|
|
|
else
|
|
|
|
|
unset CC
|
|
|
|
|
fi
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
AC_PROG_CC
|
|
|
|
|
AC_PROG_CPP
|
|
|
|
|
|
|
|
|
|
dnl# These must be run after AC_PROG_CC but before any other macros that use
|
|
|
|
|
dnl# the C compiler
|
|
|
|
|
AC_AIX
|
|
|
|
|
AC_ISC_POSIX
|
|
|
|
|
AC_MINIX
|
|
|
|
|
|
|
|
|
|
dnl# At least make the attempt to support CygWin32
|
|
|
|
|
AC_CYGWIN
|
|
|
|
|
AC_ARG_PROGRAM
|
|
|
|
|
|
|
|
|
|
AM_PROG_LIBTOOL
|
|
|
|
|
|
|
|
|
|
dnl# Where are we?
|
|
|
|
|
AC_MSG_CHECKING(for distribution root)
|
|
|
|
|
DIST_ROOT=`pwd`
|
|
|
|
|
AC_SUBST(DIST_ROOT)
|
|
|
|
|
AC_MSG_RESULT($DIST_ROOT)
|
|
|
|
|
|
|
|
|
|
AC_GCC_TRADITIONAL
|
|
|
|
|
|
|
|
|
|
dnl # If using gcc, use -O2. If -g works with it, use that too
|
|
|
|
|
if test "${CFLAGS_GIVEN}" -ne 1; then
|
|
|
|
|
if test "$GCC" = "yes"; then
|
|
|
|
|
if test "$ac_cv_prog_cc_g" = "yes"; then
|
|
|
|
|
CCOPTS='-g -O2'
|
|
|
|
|
else
|
|
|
|
|
CCOPTS='-O2'
|
|
|
|
|
fi
|
|
|
|
|
CFLAGS="$CCOPTS"
|
|
|
|
|
fi
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
AC_PROG_INSTALL
|
|
|
|
|
|
|
|
|
|
dnl# Check for host system type
|
|
|
|
|
AC_CANONICAL_HOST
|
|
|
|
|
|
|
|
|
|
dnl# Check the sanity of what we've done so far
|
|
|
|
|
AM_SANITY_CHECK
|
|
|
|
|
|
|
|
|
|
dnl# Most people don't want the developer-only clutter
|
|
|
|
|
AM_MAINTAINER_MODE
|
|
|
|
|
|
|
|
|
|
dnl# If it's there, what the hell?
|
|
|
|
|
AM_WITH_DMALLOC
|
|
|
|
|
|
|
|
|
|
dnl# Look for needed programs
|
|
|
|
|
AC_CHECK_PROG(SED, sed, sed, false)
|
|
|
|
|
AC_CHECK_PROG(RM, rm, rm, true)
|
|
|
|
|
AC_CHECK_PROG(CP, cp, cp, false)
|
|
|
|
|
AC_CHECK_PROG(CHMOD, chmod, chmod, true)
|
|
|
|
|
AC_CHECK_PROG(TAR, tar, tar, tar)
|
|
|
|
|
AC_CHECK_PROG(MKDIR, mkdir, mkdir, false)
|
|
|
|
|
AC_CHECK_PROG(CTAGS, ctags, ctags, true)
|
|
|
|
|
AC_CHECK_PROG(AR, ar, ar, false)
|
|
|
|
|
AC_CHECK_PROG(MV, mv, mv, true)
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
AC_CHECK_PROG(TIC, tic, tic, true)
|
1999-08-17 16:01:18 -07:00
|
|
|
AC_LN_S
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
AC_PATH_PROG(PERL, perl, /usr/bin/perl, $PATH:/usr/bin:/bin:/usr/local/bin:/usr/ccs/bin:/usr/contrib/bin)
|
|
|
|
|
AC_PATH_PROG(AWK, awk, /usr/bin/awk, $PATH:/usr/bin:/bin:/usr/local/bin:/usr/ccs/bin:/usr/contrib/bin)
|
|
|
|
|
export PERL AWK
|
1999-08-17 16:01:18 -07:00
|
|
|
|
|
|
|
|
AC_CHECK_SIZEOF(int, 4)
|
|
|
|
|
AC_CHECK_SIZEOF(long, 4)
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
AC_CHECK_SIZEOF(void *, 4)
|
1999-08-17 16:01:18 -07:00
|
|
|
AC_CHECK_SIZEOF(long long, 8)
|
2000-05-04 00:22:07 -07:00
|
|
|
AC_C_BIGENDIAN
|
1999-08-17 16:01:18 -07:00
|
|
|
|
|
|
|
|
AC_C_CONST
|
|
|
|
|
AC_C_INLINE
|
|
|
|
|
AC_PATH_XTRA
|
|
|
|
|
|
2000-08-31 22:46:04 -07:00
|
|
|
if test ! -z "$X_CFLAGS"; then
|
|
|
|
|
if test -z "$CPPFLAGS"; then
|
|
|
|
|
CPPFLAGS="$X_CFLAGS"
|
|
|
|
|
else
|
|
|
|
|
CPPFLAGS="$CPPFLAGS $X_CFLAGS"
|
|
|
|
|
fi
|
1999-08-17 16:01:18 -07:00
|
|
|
fi
|
2000-08-31 22:46:04 -07:00
|
|
|
if test ! -z "$X_LIBS"; then
|
|
|
|
|
if test -z "$LDFLAGS"; then
|
|
|
|
|
LDFLAGS="$X_LIBS"
|
|
|
|
|
else
|
|
|
|
|
LDFLAGS="$LDFLAGS $X_LIBS"
|
|
|
|
|
fi
|
1999-08-17 16:01:18 -07:00
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
dnl# Checks for header files.
|
|
|
|
|
AC_HEADER_SYS_WAIT
|
|
|
|
|
AC_CHECK_HEADERS(fcntl.h termios.h \
|
|
|
|
|
sys/ioctl.h sys/select.h sys/time.h \
|
2000-08-30 22:41:44 -07:00
|
|
|
sys/sockio.h sys/byteorder.h malloc.h \
|
1999-08-17 16:01:18 -07:00
|
|
|
utmpx.h unistd.h bsd/signal.h regex.h \
|
2000-11-14 17:30:02 -08:00
|
|
|
regexp.h stdarg.h X11/Xmu/Atoms.h \
|
|
|
|
|
X11/Sunkeysym.h)
|
1999-08-17 16:01:18 -07:00
|
|
|
AC_HEADER_TIME
|
|
|
|
|
|
|
|
|
|
dnl# Missing typedefs and replacements
|
|
|
|
|
AC_TYPE_MODE_T
|
|
|
|
|
AC_CHECK_TYPE(off_t, long)
|
|
|
|
|
AC_TYPE_PID_T
|
|
|
|
|
AC_TYPE_UID_T
|
|
|
|
|
|
|
|
|
|
dnl# Checks for library functions.
|
|
|
|
|
AC_TYPE_SIGNAL
|
2000-08-30 22:41:44 -07:00
|
|
|
AC_CHECK_FUNCS(atexit _exit unsetenv setutent \
|
|
|
|
|
seteuid memmove putenv strsep setresuid setresgid \
|
|
|
|
|
memmem usleep snprintf strcasestr strcasechr \
|
|
|
|
|
strcasepbrk strrev)
|
1999-08-17 18:12:47 -07:00
|
|
|
dps_snprintf_oflow()
|
2000-08-31 22:46:04 -07:00
|
|
|
AC_CHECK_LIB(m, pow)
|
|
|
|
|
|
|
|
|
|
dnl# Portability checks for various functions
|
|
|
|
|
AC_SEARCH_LIBS(login, bsd ucb util)
|
|
|
|
|
AC_SEARCH_LIBS(logout, util)
|
|
|
|
|
AC_SEARCH_LIBS(getpwuid, sun)
|
1999-08-17 16:01:18 -07:00
|
|
|
|
1999-10-11 11:37:55 -07:00
|
|
|
dnl#
|
|
|
|
|
dnl# Utility stuff
|
|
|
|
|
dnl#
|
1999-08-17 16:01:18 -07:00
|
|
|
dnl# Did they want debugging?
|
|
|
|
|
AC_MSG_CHECKING(for debugging level)
|
2000-06-26 16:37:05 -07:00
|
|
|
AC_ARG_WITH(debugging, [ --with-debugging[=num] enable debugging output, num is an integer 0-9],
|
1999-08-17 16:01:18 -07:00
|
|
|
if test "$withval" = "yes"; then
|
|
|
|
|
withval=4
|
|
|
|
|
else
|
|
|
|
|
:
|
|
|
|
|
fi
|
|
|
|
|
if test "$withval" != "no"; then
|
|
|
|
|
echo "$withval"
|
|
|
|
|
AC_DEFINE_UNQUOTED(DEBUG, $withval)
|
|
|
|
|
else
|
|
|
|
|
echo "no debugging"
|
2000-09-01 15:14:17 -07:00
|
|
|
AC_DEFINE_UNQUOTED(DEBUG, 0)
|
1999-08-17 16:01:18 -07:00
|
|
|
fi, echo "4"
|
|
|
|
|
AC_DEFINE_UNQUOTED(DEBUG, 4)
|
|
|
|
|
)
|
|
|
|
|
|
1999-10-12 11:51:56 -07:00
|
|
|
AC_CHECK_FUNC(ptsname,
|
|
|
|
|
HAVE_PTSNAME=yes
|
|
|
|
|
)
|
|
|
|
|
AC_CHECK_FUNC(grantpt,
|
|
|
|
|
HAVE_GRANTPT=yes
|
|
|
|
|
)
|
|
|
|
|
AC_CHECK_FUNC(unlockpt,
|
|
|
|
|
HAVE_UNLOCKPT=yes
|
|
|
|
|
)
|
1999-10-11 11:37:55 -07:00
|
|
|
dnl# Check for the appropriate pty mechanism
|
|
|
|
|
AC_MSG_CHECKING(for pty mechanism)
|
|
|
|
|
PTY_MECH=""
|
1999-10-27 06:39:30 -07:00
|
|
|
if test -c /dev/ptc ; then
|
1999-10-11 11:37:55 -07:00
|
|
|
AC_DEFINE(HAVE_DEV_PTC)
|
|
|
|
|
PTY_MECH="AIX $PTY_MECH"
|
|
|
|
|
fi
|
1999-10-12 11:51:56 -07:00
|
|
|
if test -r /dev/ptmx -a ! -z "$HAVE_PTSNAME" -a ! -z "$HAVE_GRANTPT" -a ! -z "$HAVE_UNLOCKPT"; then
|
1999-10-11 11:37:55 -07:00
|
|
|
AC_DEFINE(HAVE_DEV_PTMX)
|
|
|
|
|
PTY_MECH="SVR4 $PTY_MECH"
|
|
|
|
|
fi
|
1999-10-12 11:51:56 -07:00
|
|
|
if test -c /dev/ptyp128 ; then
|
1999-10-11 11:37:55 -07:00
|
|
|
AC_DEFINE(HAVE_SCO_PTYS)
|
|
|
|
|
PTY_MECH="SCO $PTY_MECH"
|
|
|
|
|
fi
|
|
|
|
|
if test "X$PTY_MECH" = "X"; then
|
|
|
|
|
AC_MSG_RESULT(generic pty's only)
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT($PTY_MECH)
|
|
|
|
|
fi
|
1999-12-30 04:44:45 -08:00
|
|
|
AC_MSG_CHECKING(for pty group)
|
|
|
|
|
AC_ARG_WITH(pty-group,
|
|
|
|
|
[ --with-pty-group[=gid] specify the group that should own pty files],
|
|
|
|
|
if test "$withval" = "yes"; then
|
|
|
|
|
PTY_GRP_NAME=`ls -1l /dev/pty* 2>/dev/null | head -n 1 | awk '{print $4}'`
|
|
|
|
|
if test ! -z "$PTY_GRP_NAME"; then
|
|
|
|
|
AC_MSG_RESULT($PTY_GRP_NAME)
|
|
|
|
|
AC_DEFINE_UNQUOTED(PTY_GRP_NAME, "$PTY_GRP_NAME")
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(unable to determine. This feature will not be enabled.)
|
|
|
|
|
fi
|
|
|
|
|
elif test "$withval" = "no"; then
|
|
|
|
|
AC_MSG_RESULT(none)
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT($withval)
|
|
|
|
|
AC_DEFINE_UNQUOTED(PTY_GRP_NAME, "$withval")
|
|
|
|
|
fi
|
|
|
|
|
,
|
|
|
|
|
PTY_GRP_NAME=`ls -1l /dev/pty* 2>/dev/null | head -n 1 | awk '{print $4}'`
|
|
|
|
|
if test ! -z "$PTY_GRP_NAME"; then
|
|
|
|
|
AC_MSG_RESULT($PTY_GRP_NAME)
|
|
|
|
|
AC_DEFINE_UNQUOTED(PTY_GRP_NAME, "$PTY_GRP_NAME")
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(none)
|
|
|
|
|
fi
|
|
|
|
|
)
|
2000-12-29 14:59:13 -08:00
|
|
|
AC_MSG_CHECKING(for saved uids)
|
|
|
|
|
AC_ARG_WITH(saved-uids, [ --with(out)-saved-uids specify that your OS has (does not have) saved uids, default is to guess],
|
|
|
|
|
if test "$withval" = "yes"; then
|
|
|
|
|
AC_MSG_RESULT(user specified yes)
|
|
|
|
|
HAVE_SAVED_UIDS=1
|
|
|
|
|
elif test "$withval" = "no"; then
|
|
|
|
|
AC_MSG_RESULT(user specified no)
|
|
|
|
|
HAVE_SAVED_UIDS=0
|
|
|
|
|
fi
|
|
|
|
|
)
|
|
|
|
|
if test "x$HAVE_SAVED_UIDS" = "x"; then
|
|
|
|
|
case `uname -s` in
|
|
|
|
|
Linux | linux | GNU*Linux) HAVE_SAVED_UIDS=1 ;;
|
|
|
|
|
HP*UX | hp*ux) HAVE_SAVED_UIDS=1 ;;
|
|
|
|
|
AIX | aix) HAVE_SAVED_UIDS=1 ;;
|
|
|
|
|
Solaris | SunOS | [Ss]un) HAVE_SAVED_UIDS=1 ;;
|
|
|
|
|
*BSD) HAVE_SAVED_UIDS=0 ;;
|
|
|
|
|
esac
|
|
|
|
|
if test "x$HAVE_SAVED_UIDS" = "x"; then
|
|
|
|
|
AC_MSG_RESULT(unknown...assuming no support)
|
|
|
|
|
HAVE_SAVED_UIDS=0
|
|
|
|
|
elif test $HAVE_SAVED_UIDS -eq 1; then
|
|
|
|
|
AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(HAVE_SAVED_UIDS)
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
fi
|
|
|
|
|
fi
|
1999-10-11 11:37:55 -07:00
|
|
|
|
2000-08-31 22:46:04 -07:00
|
|
|
dnl#
|
|
|
|
|
dnl# X LIBRARIES
|
|
|
|
|
dnl#
|
|
|
|
|
AC_CHECK_LIB(X11, XOpenDisplay, , [
|
|
|
|
|
echo "ERROR: You need libX11 to build Eterm. Verify that you have libX11.a or";
|
|
|
|
|
echo " libX11.so installed and that it is located in the X libraries";
|
|
|
|
|
echo " directory shown above. If it is in a different directory, try using";
|
|
|
|
|
echo " the --x-libraries parameter to configure.";
|
|
|
|
|
AC_MSG_ERROR([Fatal: libX11 not found.])])
|
|
|
|
|
AC_CHECK_LIB(Xext, XextAddDisplay, , [
|
|
|
|
|
echo "ERROR: You need libXext to build Eterm. Verify that you have libXext.a or";
|
|
|
|
|
echo " libXext.so installed and that it is located in the X libraries";
|
|
|
|
|
echo " directory shown above. If it is in a different directory, try using";
|
|
|
|
|
echo " the --x-libraries parameter to configure.";
|
|
|
|
|
AC_MSG_ERROR([Fatal: libXext not found.])])
|
|
|
|
|
|
|
|
|
|
AC_CHECK_LIB(Xext, XShapeQueryExtension, AC_DEFINE(HAVE_X_SHAPE_EXT))
|
|
|
|
|
|
|
|
|
|
# check if we need X_LOCALE definition
|
2001-07-03 18:02:37 -07:00
|
|
|
AC_CHECK_LIB(X11, _Xsetlocale, AC_DEFINE(X_LOCALE), AC_DEFINE(NO_XLOCALE))
|
2000-08-31 22:46:04 -07:00
|
|
|
|
|
|
|
|
# For multibyte selection handling
|
|
|
|
|
if test "$MULTICHAR_ENCODING" != "none"; then
|
|
|
|
|
AC_CHECK_LIB(Xmu, XmuInternAtom)
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
# check X11R6 for XIM
|
|
|
|
|
if test "$XIM" = "TRUE"; then
|
|
|
|
|
AC_CHECK_LIB(X11, XRegisterIMInstantiateCallback, AC_DEFINE(USE_X11R6_XIM))
|
|
|
|
|
fi
|
|
|
|
|
|
1999-08-17 18:12:47 -07:00
|
|
|
dnl#
|
|
|
|
|
dnl# FEATURES
|
|
|
|
|
dnl#
|
1999-12-06 09:20:16 -08:00
|
|
|
AC_MSG_CHECKING(if Pablo support is wanted)
|
|
|
|
|
AC_ARG_WITH(pablo,
|
|
|
|
|
[ --with-pablo[=DIR] compile with Pablo I/O Tracing support (using Pablo prefix DIR)],
|
|
|
|
|
if test "$withval" != "no"; then
|
|
|
|
|
AC_MSG_RESULT(yes)
|
|
|
|
|
if test "$withval" != "yes"; then
|
|
|
|
|
CPPFLAGS="$CPPFLAGS -I${withval}/include"
|
|
|
|
|
LDFLAGS="$LDFLAGS -L${withval}/lib"
|
|
|
|
|
fi
|
|
|
|
|
AC_CHECK_HEADER(IOTrace.h,
|
|
|
|
|
AC_CHECK_LIB(PabloTraceExt, initIOTrace,
|
|
|
|
|
AC_DEFINE(IOTRACE)
|
|
|
|
|
LIBS="$LIBS -lPabloTraceExt -lPabloTrace"
|
|
|
|
|
echo "Pablo support enabled. Headers in ${withval}/include. Libraries in ${withval}/lib."
|
|
|
|
|
,
|
|
|
|
|
echo "*** ERROR: Pablo support was requested but the Pablo libraries could not be"
|
|
|
|
|
echo "*** found. Please check config.log for further information."
|
|
|
|
|
echo "*** Pablo support will NOT be included."
|
|
|
|
|
, -lPabloTrace)
|
|
|
|
|
,
|
|
|
|
|
echo "*** ERROR: Pablo support was requested but the Pablo header files could not be"
|
|
|
|
|
echo "*** found. Please check the value you passed to --with-pablo."
|
|
|
|
|
echo "*** Pablo support will NOT be included.")
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
fi, AC_MSG_RESULT(no)
|
|
|
|
|
)
|
2000-01-11 23:49:02 -08:00
|
|
|
AC_MSG_CHECKING(if profiling macros should be included)
|
|
|
|
|
AC_ARG_ENABLE(profile,
|
|
|
|
|
[ --enable-profile compile with code profiling macros enabled],
|
|
|
|
|
if test "$enableval" = "yes"; then
|
|
|
|
|
AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(ENABLE_PROFILE)
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
fi, AC_MSG_RESULT(no)
|
|
|
|
|
)
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_MSG_CHECKING(for pixmap support)
|
1999-08-17 16:01:18 -07:00
|
|
|
AC_ARG_WITH(imlib,
|
1999-08-17 18:12:47 -07:00
|
|
|
[ --with-imlib[=DIR] compile with Imlib support (Imlib residing in DIR/lib) (default)],
|
1999-08-17 16:01:18 -07:00
|
|
|
if test "$withval" != "no"; then
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_MSG_RESULT(yes)
|
Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-12 21:19:05 -07:00
|
|
|
if test "$withval" != "yes"; then
|
2000-08-31 22:46:04 -07:00
|
|
|
CPPFLAGS="$CPPFLAGS -I${withval}/include"
|
Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-12 21:19:05 -07:00
|
|
|
LDFLAGS="$LDFLAGS -L${withval}/lib"
|
|
|
|
|
fi
|
|
|
|
|
USE_IMLIB=1
|
1999-08-17 18:12:47 -07:00
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
GRLIBS=""
|
Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-12 21:19:05 -07:00
|
|
|
USE_IMLIB=0
|
2000-05-02 16:46:08 -07:00
|
|
|
AC_WARN(*** Pixmap support has been disabled at your request. This ***)
|
|
|
|
|
AC_WARN(*** is generally a bad idea since it really doesn't save ***)
|
|
|
|
|
AC_WARN(*** much memory. And the developers almost never test that ***)
|
|
|
|
|
AC_WARN(*** configuration. So I'd reconsider if I were you.... ***)
|
1999-08-17 18:12:47 -07:00
|
|
|
fi, AC_MSG_RESULT(yes)
|
Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-12 21:19:05 -07:00
|
|
|
USE_IMLIB=1
|
1999-08-17 18:12:47 -07:00
|
|
|
)
|
Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-12 21:19:05 -07:00
|
|
|
if test $USE_IMLIB -eq 1 ; then
|
2000-08-31 22:46:04 -07:00
|
|
|
AC_CHECK_LIB(dl, dlopen, GRLIBS="-ldl", , $GRLIBS)
|
|
|
|
|
AC_CHECK_LIB(ttf, TT_Init_FreeType, GRLIBS="-lttf $GRLIBS", , $GRLIBS)
|
Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-12 21:19:05 -07:00
|
|
|
AC_CHECK_LIB(Imlib2, imlib_create_image,
|
2000-04-27 19:42:26 -07:00
|
|
|
GRLIBS="-lImlib2 $GRLIBS"
|
2000-08-31 22:46:04 -07:00
|
|
|
AC_DEFINE(HAVE_LIBIMLIB2)
|
Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-12 21:19:05 -07:00
|
|
|
AC_DEFINE(PIXMAP_SUPPORT)
|
|
|
|
|
AC_DEFINE(BACKING_STORE)
|
|
|
|
|
,
|
2000-05-02 16:46:08 -07:00
|
|
|
AC_WARN(*** Pixmap support has been disabled because Imlib2 was not found ***)
|
|
|
|
|
AC_WARN(*** or could not be linked. Eterm should still work, but it will ***)
|
|
|
|
|
AC_WARN(*** not be very happy. Check config.log for more detailed ***)
|
|
|
|
|
AC_WARN(*** information on why my attempt to link with Imlib2 failed. ***)
|
2000-08-31 22:46:04 -07:00
|
|
|
, $GRLIBS)
|
Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-12 21:19:05 -07:00
|
|
|
|
|
|
|
|
fi
|
|
|
|
|
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_MSG_CHECKING(for transparency support)
|
|
|
|
|
AC_ARG_ENABLE(trans,
|
Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-12 21:19:05 -07:00
|
|
|
[ --enable-trans compile with transparency support],
|
|
|
|
|
if test "$enableval" != "no"; then
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(PIXMAP_OFFSET)
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
fi, AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(PIXMAP_OFFSET)
|
|
|
|
|
)
|
2000-05-04 00:22:07 -07:00
|
|
|
|
|
|
|
|
AC_MSG_CHECKING(for MMX support)
|
|
|
|
|
HAVE_MMX=""
|
|
|
|
|
AC_ARG_ENABLE(mmx, [ --enable-mmx enable MMX assembly routines],
|
2000-11-16 15:45:01 -08:00
|
|
|
test "x$enableval" = "xyes" && HAVE_MMX="yes"
|
2000-05-04 00:22:07 -07:00
|
|
|
,
|
|
|
|
|
if test x$build_os = xlinux-gnu; then
|
|
|
|
|
grep mmx /proc/cpuinfo >/dev/null 2>&1 && HAVE_MMX="yes"
|
|
|
|
|
fi
|
|
|
|
|
)
|
2000-11-16 15:45:01 -08:00
|
|
|
if test "x$HAVE_MMX" = "xyes"; then
|
2000-05-04 00:22:07 -07:00
|
|
|
AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(HAVE_MMX)
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
fi
|
2000-11-16 15:45:01 -08:00
|
|
|
AM_CONDITIONAL(HAVE_MMX, test "x$HAVE_MMX" = "xyes")
|
2000-05-04 00:22:07 -07:00
|
|
|
|
2000-10-30 15:05:25 -08:00
|
|
|
dnl#
|
|
|
|
|
dnl# LibAST
|
|
|
|
|
dnl#
|
|
|
|
|
AC_CHECK_LIB(ast, libast_malloc, FOUND_LIBAST=1, FOUND_LIBAST=0, $GRLIBS)
|
2000-10-30 20:56:13 -08:00
|
|
|
if test "$FOUND_LIBAST" -eq "1"; then
|
|
|
|
|
AC_CHECK_PROG(LIBAST_CONFIG, libast-config, libast-config, false)
|
|
|
|
|
test "$LIBAST_CONFIG" = "false" && FOUND_LIBAST=0
|
|
|
|
|
fi
|
2000-10-30 15:05:25 -08:00
|
|
|
|
2000-10-30 20:56:13 -08:00
|
|
|
if test "$FOUND_LIBAST" -ne "1"; then
|
|
|
|
|
echo "ERROR: You need the LibAST package to build Eterm. If you already have it,";
|
|
|
|
|
echo " you may have it installed in a strange place, or you may need to run";
|
|
|
|
|
echo " /sbin/ldconfig. If you don't have it, I can download it for you.";
|
|
|
|
|
echo " Shall I retrieve and build LibAST now (y/n)?";
|
|
|
|
|
read ANS
|
|
|
|
|
if test "x$ANS" = "xy" -o "x$ANS" = "xyes" -o "x$ANS" = "xY" -o "x$ANS" = "xYES"; then
|
|
|
|
|
if test -d CVS ; then
|
|
|
|
|
# Download from CVS server
|
|
|
|
|
CVSROOT=":pserver:anonymous@cvs.enlightenment.sourceforge.net:/cvsroot/enlightenment"
|
|
|
|
|
grep $CVSROOT $HOME/.cvspass >/dev/null 2>&1 || cvs -d $CVSROOT login
|
|
|
|
|
cvs -z3 -d $CVSROOT co -d libast eterm/libast
|
|
|
|
|
(cd libast && ./autogen.sh $ac_configure_args && make install && cd .. && rm -rf libast)
|
|
|
|
|
if test $? -ne 0; then
|
|
|
|
|
echo 'ERROR: Unable to auto-get libast, sorry.' 1>&2
|
|
|
|
|
exit 1
|
|
|
|
|
fi
|
|
|
|
|
FOUND_LIBAST=1
|
|
|
|
|
AC_CHECK_PROG(LIBAST_CONFIG, libast-config, libast-config, false)
|
|
|
|
|
test "$LIBAST_CONFIG" = "false" && FOUND_LIBAST=0
|
|
|
|
|
else
|
|
|
|
|
# Download tarball
|
|
|
|
|
:
|
|
|
|
|
fi
|
|
|
|
|
fi
|
|
|
|
|
fi
|
2000-10-30 15:05:25 -08:00
|
|
|
if test "$FOUND_LIBAST" -eq "1"; then
|
|
|
|
|
if test ! -z "$LIBAST_CONFIG"; then
|
|
|
|
|
GRLIBS="-last $GRLIBS"
|
|
|
|
|
AC_DEFINE(HAVE_LIBAST)
|
2000-10-31 19:33:55 -08:00
|
|
|
test "$prefix" = "NONE" && prefix="`$LIBAST_CONFIG --prefix`"
|
2000-10-30 15:05:25 -08:00
|
|
|
CPPFLAGS="$CPPFLAGS `$LIBAST_CONFIG --cppflags`"
|
|
|
|
|
LDFLAGS="$LDFLAGS `$LIBAST_CONFIG --ldflags`"
|
|
|
|
|
SUPPORT_FLAGS="`$LIBAST_CONFIG --support`"
|
|
|
|
|
for i in $SUPPORT_FLAGS ; do
|
|
|
|
|
case $i in
|
|
|
|
|
MMX)
|
|
|
|
|
AC_DEFINE(LIBAST_MMX_SUPPORT)
|
|
|
|
|
;;
|
|
|
|
|
X11)
|
|
|
|
|
AC_DEFINE(LIBAST_X11_SUPPORT)
|
|
|
|
|
;;
|
|
|
|
|
Imlib2)
|
|
|
|
|
AC_DEFINE(LIBAST_IMLIB2_SUPPORT)
|
|
|
|
|
;;
|
|
|
|
|
esac
|
|
|
|
|
done
|
|
|
|
|
fi
|
|
|
|
|
else
|
2000-10-30 20:56:13 -08:00
|
|
|
AC_MSG_ERROR(Fatal: libast not found.)
|
2000-10-30 15:05:25 -08:00
|
|
|
fi
|
|
|
|
|
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_MSG_CHECKING(for utmp support)
|
|
|
|
|
AC_ARG_ENABLE(utmp,
|
|
|
|
|
[ --enable-utmp compile with utmp support],
|
|
|
|
|
if test "$enableval" != "no"; then
|
|
|
|
|
AC_MSG_RESULT(yes)
|
1999-12-07 17:13:44 -08:00
|
|
|
UTMP=1
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_DEFINE(UTMP_SUPPORT)
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(no)
|
1999-12-07 17:13:44 -08:00
|
|
|
UTMP=0
|
1999-08-17 18:12:47 -07:00
|
|
|
fi, AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(UTMP_SUPPORT)
|
1999-12-07 17:13:44 -08:00
|
|
|
UTMP=1
|
1999-08-17 18:12:47 -07:00
|
|
|
)
|
1999-12-07 17:13:44 -08:00
|
|
|
if test $UTMP -eq 1; then
|
2000-08-31 22:46:04 -07:00
|
|
|
AC_CHECK_LIB(utempter, addToUtmp)
|
1999-12-07 17:13:44 -08:00
|
|
|
fi
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_MSG_CHECKING(for backspace key configuration)
|
|
|
|
|
AC_ARG_WITH(backspace,
|
1999-10-04 15:24:28 -07:00
|
|
|
[ --with-backspace=KEY force backspace to send KEY (KEY is either \"bs\" for ^H or \"del\" for ^?)],
|
1999-08-17 18:12:47 -07:00
|
|
|
if test "$withval" = "bs"; then
|
|
|
|
|
AC_MSG_RESULT(forcing Backspace to send Ctrl-H)
|
|
|
|
|
AC_DEFINE(FORCE_BACKSPACE)
|
|
|
|
|
elif test "$withval" = "del"; then
|
|
|
|
|
AC_MSG_RESULT(forcing Backspace to send Ctrl-?)
|
|
|
|
|
AC_DEFINE(FORCE_DELETE)
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(default)
|
|
|
|
|
fi, AC_MSG_RESULT(default)
|
|
|
|
|
)
|
|
|
|
|
AC_MSG_CHECKING(for delete key configuration)
|
|
|
|
|
AC_ARG_WITH(delete,
|
1999-10-04 15:24:28 -07:00
|
|
|
[ --with-delete=SETTING force delete to SETTING (\"server\" to use the X server value always,
|
|
|
|
|
\"execute\" to send the old default execute escape sequence,
|
|
|
|
|
or a quoted string to use a specific string)],
|
|
|
|
|
if test "$withval" = "server"; then
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_MSG_RESULT(X server value)
|
|
|
|
|
AC_DEFINE(NO_DELETE_KEY)
|
1999-10-04 15:24:28 -07:00
|
|
|
elif test "$withval" = "no"; then
|
|
|
|
|
AC_MSG_RESULT(X server value)
|
|
|
|
|
AC_DEFINE(NO_DELETE_KEY)
|
|
|
|
|
elif test "$withval" = "execute"; then
|
|
|
|
|
AC_MSG_RESULT(send execute sequence)
|
1999-08-17 18:12:47 -07:00
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(forcing Delete to send "$withval")
|
|
|
|
|
AC_DEFINE_UNQUOTED(KS_DELETE, "$withval")
|
|
|
|
|
fi, AC_MSG_RESULT(default)
|
|
|
|
|
AC_DEFINE_UNQUOTED(KS_DELETE, "\177")
|
|
|
|
|
)
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
XTERM_HOME="\033\133H"
|
|
|
|
|
LINUX_HOME="\033\1331~"
|
|
|
|
|
AC_MSG_CHECKING(for home key configuration)
|
|
|
|
|
AC_ARG_WITH(home,
|
|
|
|
|
[ --with-home=SEQUENCE specify which sequence to use for the Home key ("xterm", "linux", or "vt102")],
|
|
|
|
|
if test "$withval" = "xterm"; then
|
|
|
|
|
AC_MSG_RESULT(emulate xterm)
|
|
|
|
|
AC_DEFINE_UNQUOTED(KS_HOME, "$XTERM_HOME")
|
|
|
|
|
elif test "$withval" = "linux"; then
|
|
|
|
|
AC_MSG_RESULT(emulate linux console/vt220)
|
|
|
|
|
AC_DEFINE_UNQUOTED(KS_HOME, "$LINUX_HOME")
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(default vt102)
|
|
|
|
|
fi, AC_MSG_RESULT(default)
|
|
|
|
|
)
|
|
|
|
|
XTERM_END="\033\133F"
|
|
|
|
|
LINUX_END="\033\1334~"
|
|
|
|
|
AC_MSG_CHECKING(for end key configuration)
|
|
|
|
|
AC_ARG_WITH(end,
|
|
|
|
|
[ --with-end=SEQUENCE specify which sequence to use for the End key ("xterm", "linux", or "vt102")],
|
|
|
|
|
if test "$withval" = "xterm"; then
|
|
|
|
|
AC_MSG_RESULT(emulate xterm)
|
|
|
|
|
AC_DEFINE_UNQUOTED(KS_END, "$XTERM_END")
|
|
|
|
|
elif test "$withval" = "linux"; then
|
|
|
|
|
AC_MSG_RESULT(emulate linux console/vt220)
|
|
|
|
|
AC_DEFINE_UNQUOTED(KS_END, "$LINUX_END")
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(default vt102)
|
|
|
|
|
fi, AC_MSG_RESULT(default)
|
|
|
|
|
)
|
Mon Jun 11 17:49:55 PDT 2001 Michael Jennings <mej@eterm.org>
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
2001-06-11 18:04:45 -07:00
|
|
|
AC_MSG_CHECKING(if mousewheel support should be enabled)
|
|
|
|
|
AC_ARG_WITH(mousewheel,
|
|
|
|
|
[ --without-mousewheel disable built-in mousewheel support],
|
|
|
|
|
if test "$withval" = "no"; then
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(MOUSEWHEEL)
|
|
|
|
|
fi, AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(MOUSEWHEEL)
|
|
|
|
|
)
|
2000-01-07 07:51:22 -08:00
|
|
|
MULTICHAR_ENCODING=""
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_MSG_CHECKING(for multi-charset support)
|
|
|
|
|
AC_ARG_ENABLE(multi-charset,
|
Fri May 26 20:43:03 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-05-26 20:41:22 -07:00
|
|
|
[ --enable-multi-charset compile with multibyte font support],
|
|
|
|
|
if test "$enableval" = "no"; then
|
|
|
|
|
MULTI_CHARSET_TYPE=""
|
1999-12-10 18:06:33 -08:00
|
|
|
else
|
Fri May 26 20:43:03 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-05-26 20:41:22 -07:00
|
|
|
MULTI_CHARSET_TYPE="$enableval"
|
|
|
|
|
fi,
|
|
|
|
|
if (xlsfonts | grep 10646 >/dev/null 2>&1); then
|
|
|
|
|
MULTI_CHARSET_TYPE="unicode"
|
|
|
|
|
else
|
|
|
|
|
MULTI_CHARSET_TYPE=""
|
|
|
|
|
fi
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
if test "x$MULTI_CHARSET_TYPE" != "x"; then
|
|
|
|
|
if test "$MULTI_CHARSET_TYPE" = "kanji"; then
|
|
|
|
|
AC_MSG_RESULT(kanji)
|
|
|
|
|
AC_DEFINE(MULTI_CHARSET)
|
|
|
|
|
DEF_FONT_IDX=0
|
|
|
|
|
MULTICHAR_ENCODING="eucj"
|
|
|
|
|
FONT0="fixed"
|
|
|
|
|
FONT1="8x16"
|
|
|
|
|
FONT2="9x18"
|
|
|
|
|
FONT3="12x24"
|
|
|
|
|
FONT4="13x26"
|
|
|
|
|
MFONT0="k14"
|
|
|
|
|
MFONT1="jiskan16"
|
|
|
|
|
MFONT2="jiskan18"
|
|
|
|
|
MFONT3="jiskan24"
|
|
|
|
|
MFONT4="jiskan26"
|
|
|
|
|
elif test "$MULTI_CHARSET_TYPE" = "euc-kr" -o "$MULTI_CHARSET_TYPE" = "euckr"; then
|
|
|
|
|
AC_MSG_RESULT(euckr)
|
|
|
|
|
AC_DEFINE(MULTI_CHARSET)
|
|
|
|
|
DEF_FONT_IDX=1
|
|
|
|
|
MULTICHAR_ENCODING="euckr"
|
|
|
|
|
FONT0="7x14"
|
|
|
|
|
FONT1="8x16"
|
|
|
|
|
FONT2="9x18"
|
|
|
|
|
FONT3="10x20"
|
|
|
|
|
FONT4="12x24"
|
|
|
|
|
MFONT0="-*-gulim-medium-r-normal--14-*-*-*-*-140-ksc5601.1987-0"
|
|
|
|
|
MFONT1="-*-gulim-medium-r-normal--16-*-*-*-*-160-ksc5601.1987-0"
|
|
|
|
|
MFONT2="-*-gulim-medium-r-normal--18-*-*-*-*-180-ksc5601.1987-0"
|
|
|
|
|
MFONT3="-*-gulim-medium-r-normal--20-*-*-*-*-200-ksc5601.1987-0"
|
|
|
|
|
MFONT4="-*-gulim-medium-r-normal--24-*-*-*-*-240-ksc5601.1987-0"
|
|
|
|
|
elif test "$MULTI_CHARSET_TYPE" = "unicode" -o "$MULTI_CHARSET_TYPE" = "utf-8" -o "$MULTI_CHARSET_TYPE" = "utf8"; then
|
|
|
|
|
AC_MSG_RESULT(ISO-10646)
|
|
|
|
|
AC_DEFINE(MULTI_CHARSET)
|
|
|
|
|
DEF_FONT_IDX=2
|
|
|
|
|
MULTICHAR_ENCODING="iso-10646"
|
|
|
|
|
MFONT0="-misc-fixed-medium-r-normal--7-70-75-75-c-50-iso10646-1"
|
|
|
|
|
MFONT1="-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso10646-1"
|
|
|
|
|
MFONT2="-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1"
|
|
|
|
|
MFONT3="-misc-fixed-medium-r-normal--14-130-75-75-c-70-iso10646-1"
|
|
|
|
|
MFONT4="-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1"
|
|
|
|
|
FONT0="5x7"
|
|
|
|
|
FONT1="6x10"
|
|
|
|
|
FONT2="fixed"
|
|
|
|
|
FONT3="8x13"
|
|
|
|
|
FONT4="9x15"
|
2000-11-09 19:26:04 -08:00
|
|
|
elif test "$MULTI_CHARSET_TYPE" = "big5"; then
|
|
|
|
|
AC_MSG_RESULT(big5)
|
|
|
|
|
AC_DEFINE(MULTI_CHARSET)
|
|
|
|
|
DEF_FONT_IDX=0
|
|
|
|
|
MULTICHAR_ENCODING="big5"
|
|
|
|
|
FONT0="8x16"
|
|
|
|
|
FONT1="9x18"
|
|
|
|
|
FONT2="10x20"
|
|
|
|
|
FONT3="12x24"
|
|
|
|
|
FONT4="13x26"
|
|
|
|
|
MFONT0="-*-ming-medium-r-normal--16-*-*-*-c-*-big5-0"
|
|
|
|
|
MFONT1="-*-ming-medium-r-normal--18-*-*-*-c-*-big5-0"
|
|
|
|
|
MFONT2="-*-ming-medium-r-normal--20-*-*-*-c-*-big5-0"
|
|
|
|
|
MFONT3="-*-ming-medium-r-normal--24-*-*-*-c-*-big5-0"
|
|
|
|
|
MFONT4="-*-ming-medium-r-normal--26-*-*-*-c-*-big5-0"
|
Fri May 26 20:43:03 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-05-26 20:41:22 -07:00
|
|
|
else
|
|
|
|
|
MULTI_CHARSET_TYPE=""
|
|
|
|
|
fi
|
|
|
|
|
fi
|
|
|
|
|
if test "x$MULTI_CHARSET_TYPE" = "x"; then
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
DEF_FONT_IDX=2
|
|
|
|
|
MULTICHAR_ENCODING=none
|
|
|
|
|
MFONT0=none
|
|
|
|
|
MFONT1=none
|
|
|
|
|
MFONT2=none
|
|
|
|
|
MFONT3=none
|
|
|
|
|
MFONT4=none
|
|
|
|
|
FONT0="5x7"
|
|
|
|
|
FONT1="6x10"
|
|
|
|
|
FONT2="fixed"
|
|
|
|
|
FONT3="8x13"
|
|
|
|
|
FONT4="9x15"
|
|
|
|
|
fi
|
2000-01-07 07:51:22 -08:00
|
|
|
|
|
|
|
|
AC_DEFINE_UNQUOTED(DEF_FONT_IDX, $DEF_FONT_IDX)
|
|
|
|
|
AC_DEFINE_UNQUOTED(FONT0, "$FONT0")
|
|
|
|
|
AC_DEFINE_UNQUOTED(FONT1, "$FONT1")
|
|
|
|
|
AC_DEFINE_UNQUOTED(FONT2, "$FONT2")
|
|
|
|
|
AC_DEFINE_UNQUOTED(FONT3, "$FONT3")
|
|
|
|
|
AC_DEFINE_UNQUOTED(FONT4, "$FONT4")
|
|
|
|
|
AC_SUBST(DEF_FONT_IDX)
|
|
|
|
|
AC_SUBST(FONT0)
|
|
|
|
|
AC_SUBST(FONT1)
|
|
|
|
|
AC_SUBST(FONT2)
|
|
|
|
|
AC_SUBST(FONT3)
|
|
|
|
|
AC_SUBST(FONT4)
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
export FONT0 FONT1 FONT2 FONT3 FONT4 DEF_FONT_IDX
|
2000-01-07 07:51:22 -08:00
|
|
|
|
|
|
|
|
AC_DEFINE_UNQUOTED(MULTICHAR_ENCODING, "$MULTICHAR_ENCODING")
|
|
|
|
|
AC_DEFINE_UNQUOTED(MFONT0, "$MFONT0")
|
|
|
|
|
AC_DEFINE_UNQUOTED(MFONT1, "$MFONT1")
|
|
|
|
|
AC_DEFINE_UNQUOTED(MFONT2, "$MFONT2")
|
|
|
|
|
AC_DEFINE_UNQUOTED(MFONT3, "$MFONT3")
|
|
|
|
|
AC_DEFINE_UNQUOTED(MFONT4, "$MFONT4")
|
|
|
|
|
AC_SUBST(MULTICHAR_ENCODING)
|
|
|
|
|
AC_SUBST(MFONT0)
|
|
|
|
|
AC_SUBST(MFONT1)
|
|
|
|
|
AC_SUBST(MFONT2)
|
|
|
|
|
AC_SUBST(MFONT3)
|
|
|
|
|
AC_SUBST(MFONT4)
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
export MFONT0 MFONT1 MFONT2 MFONT3 MFONT4 MULTICHAR_ENCODING
|
2000-01-07 07:51:22 -08:00
|
|
|
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_MSG_CHECKING(for XIM support)
|
|
|
|
|
AC_ARG_ENABLE(xim,
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
[ --enable-xim compile with XIM support (default)],
|
|
|
|
|
if test "$enableval" = "no"; then
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
XIM="FALSE"
|
|
|
|
|
else
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(USE_XIM)
|
|
|
|
|
XIM="TRUE"
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
fi, AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(USE_XIM)
|
|
|
|
|
XIM="TRUE"
|
1999-08-17 18:12:47 -07:00
|
|
|
)
|
Fri Feb 18 21:09:29 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-18 22:29:37 -08:00
|
|
|
|
1999-08-17 18:12:47 -07:00
|
|
|
AC_MSG_CHECKING(for Greek keyboard support)
|
|
|
|
|
AC_ARG_ENABLE(greek,
|
|
|
|
|
[ --enable-greek compile with support for Greek keyboards],
|
|
|
|
|
if test "$enableval" = "yes"; then
|
|
|
|
|
AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(GREEK_SUPPORT)
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
fi, AC_MSG_RESULT(no)
|
|
|
|
|
)
|
Fri Feb 18 21:09:29 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-18 22:29:37 -08:00
|
|
|
|
|
|
|
|
CONFIG_BUFF_SIZE=20480
|
|
|
|
|
AC_MSG_CHECKING(for the buffer size of the config file parser)
|
|
|
|
|
AC_ARG_WITH(config-buffer-size,
|
Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-12 21:19:05 -07:00
|
|
|
[ --with-config-buffer-size
|
|
|
|
|
specifies the size of the buffer Eterm uses for parsing the config file (default is 20 Kb)],
|
Fri Feb 18 21:09:29 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-18 22:29:37 -08:00
|
|
|
if test "$withval" != "yes" -a "$withval" != "no"; then
|
|
|
|
|
CONFIG_BUFF_SIZE=$withval
|
|
|
|
|
fi)
|
|
|
|
|
AC_MSG_RESULT($CONFIG_BUFF_SIZE bytes)
|
|
|
|
|
AC_DEFINE_UNQUOTED(CONFIG_BUFF, $CONFIG_BUFF_SIZE)
|
|
|
|
|
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
AC_ARG_WITH(terminfo,
|
|
|
|
|
[ --without-terminfo do not compile the Eterm terminfo file],
|
Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-12 21:19:05 -07:00
|
|
|
if test "$withval" = "no"; then
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
TIC=true
|
|
|
|
|
fi)
|
Fri Feb 18 21:09:29 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-18 22:29:37 -08:00
|
|
|
|
1999-12-10 18:06:33 -08:00
|
|
|
AC_ARG_WITH(theme-update,
|
|
|
|
|
[ --with-theme-update existing themes will be forceably removed and new ones installed],
|
|
|
|
|
if test "$withval" = "yes"; then
|
|
|
|
|
REMOVE_THEMES=yes
|
|
|
|
|
else
|
|
|
|
|
REMOVE_THEMES=no
|
|
|
|
|
fi, REMOVE_THEMES=no
|
|
|
|
|
)
|
|
|
|
|
AC_SUBST(REMOVE_THEMES)
|
|
|
|
|
|
1999-10-07 12:47:14 -07:00
|
|
|
dnl# AC_MSG_CHECKING(which threads library to use)
|
|
|
|
|
dnl# AC_ARG_WITH(threads,
|
|
|
|
|
dnl# [ --with-threads[=STYLE] compile with threads support, STYLE is either "posix" or blank
|
|
|
|
|
dnl# (disabled by default)],
|
|
|
|
|
dnl# case $withval in
|
|
|
|
|
dnl# [yes | posix )]
|
|
|
|
|
dnl# AC_MSG_RESULT(POSIX)
|
|
|
|
|
dnl# THREADS_LIB=posix
|
|
|
|
|
dnl# ;;
|
|
|
|
|
dnl# [* )]
|
|
|
|
|
dnl# AC_MSG_RESULT(none)
|
|
|
|
|
dnl# ;;
|
|
|
|
|
dnl# esac
|
|
|
|
|
dnl# , AC_MSG_RESULT(none))
|
|
|
|
|
dnl# if test "$THREADS_LIB" = "posix"; then
|
2000-08-31 22:46:04 -07:00
|
|
|
dnl# AC_CHECK_LIB(pthread, pthread_create, CPPFLAGS="$CPPFLAGS -D_REENTRANT" ; THREADLIBS="-lpthread"
|
1999-10-07 12:47:14 -07:00
|
|
|
dnl# AC_DEFINE(USE_POSIX_THREADS)
|
|
|
|
|
dnl# AC_DEFINE(MUTEX_SYNCH)
|
|
|
|
|
dnl# , , -D_REENTRANT -L/usr/lib -L/lib -L/usr/local/lib)
|
|
|
|
|
dnl# fi
|
1999-08-17 16:01:18 -07:00
|
|
|
|
|
|
|
|
AC_PREFIX(Eterm)
|
|
|
|
|
AC_PREFIX(gcc)
|
2000-01-12 00:14:45 -08:00
|
|
|
if test "$prefix" = "NONE"; then
|
|
|
|
|
prefix=$ac_default_prefix
|
|
|
|
|
fi
|
Wed Apr 5 21:48:39 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-05 21:52:52 -07:00
|
|
|
if test "$exec_prefix" = "NONE"; then
|
|
|
|
|
exec_prefix=$prefix
|
|
|
|
|
fi
|
2000-01-12 00:14:45 -08:00
|
|
|
|
1999-08-17 16:01:18 -07:00
|
|
|
dnl Stack Tracing toys
|
|
|
|
|
AC_ARG_ENABLE(stack-trace, [ --disable-stack-trace disable stack trace on abnormal termination],
|
|
|
|
|
if test "$enableval" = "no"; then
|
|
|
|
|
AC_DEFINE(NO_STACK_TRACE)
|
|
|
|
|
NO_STACK_TRACE=1
|
|
|
|
|
fi
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
if test "$NO_STACK_TRACE" != "1"; then
|
|
|
|
|
AC_PATH_PROG(DBX, dbx, no)
|
|
|
|
|
if test "$DBX" != "no"; then
|
|
|
|
|
AC_DEFINE_UNQUOTED(DBX, "$DBX")
|
|
|
|
|
fi
|
|
|
|
|
AC_PATH_PROG(GDB, gdb, no)
|
|
|
|
|
if test "$GDB" != "no"; then
|
|
|
|
|
AC_DEFINE_UNQUOTED(GDB, "$GDB")
|
|
|
|
|
fi
|
|
|
|
|
AC_PATH_PROG(PSTACK, pstack, no, $PATH:/usr/proc/bin:/usr/sbin)
|
|
|
|
|
if test "$PSTACK" != "no"; then
|
|
|
|
|
AC_DEFINE_UNQUOTED(PSTACK, "$PSTACK")
|
|
|
|
|
fi
|
|
|
|
|
AC_CHECK_LIB(cl, U_STACK_TRACE, LIBS="$LIBS -lcl")
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
AC_MSG_CHECKING(for Linux 2.1 or higher)
|
|
|
|
|
OS_NAME=`uname -s`
|
|
|
|
|
if test "$OS_NAME" = "Linux"; then
|
|
|
|
|
OS_REV=`uname -r`
|
|
|
|
|
OS_MAJOR=`echo $OS_REV | cut -d. -f1`
|
|
|
|
|
OS_MINOR=`echo $OS_REV | cut -d. -f2`
|
|
|
|
|
if test "$OS_MAJOR" -ge "2" -a "$OS_MINOR" -ge "1"; then
|
|
|
|
|
AC_MSG_RESULT(yes)
|
|
|
|
|
AC_DEFINE(NEED_LINUX_HACK)
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
fi
|
|
|
|
|
else
|
|
|
|
|
AC_MSG_RESULT(no)
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
dnl# Enable/disable humor
|
|
|
|
|
AC_ARG_WITH(sense-of-humor, [ --without-sense-of-humor Specify this if you have no sense of humor],
|
|
|
|
|
if test "$withval" = "no"; then
|
|
|
|
|
HUMOR=none
|
|
|
|
|
fi)
|
|
|
|
|
|
|
|
|
|
if test -z "$HUMOR"; then
|
|
|
|
|
AC_CHECK_LIB(Kenny, life_signs, , [
|
|
|
|
|
echo " Oh my god, they killed Kenny! You bastards!"
|
|
|
|
|
])
|
|
|
|
|
fi
|
|
|
|
|
|
Wed Apr 5 21:48:39 PDT 2000 Michael Jennings <mej@eterm.org>
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
2000-04-05 21:52:52 -07:00
|
|
|
CONFIG_SEARCH_PATH=`eval eval eval eval eval echo "${datadir}/$PACKAGE/themes:${datadir}/$PACKAGE"`
|
|
|
|
|
AC_DEFINE_UNQUOTED(CONFIG_SEARCH_PATH, "~/.Eterm/themes:~/.Eterm:$CONFIG_SEARCH_PATH")
|
|
|
|
|
# Do replacements on theme files and such. All variables to be replaced
|
|
|
|
|
# by this routine MUST be exported before the awk script runs.
|
|
|
|
|
if test "X$PKGDATADIR" = "X" ; then
|
|
|
|
|
PKGDATADIR=`eval eval eval eval echo "$datadir/$PACKAGE"`
|
|
|
|
|
fi
|
|
|
|
|
export PKGDATADIR
|
|
|
|
|
AC_DEFINE_UNQUOTED(PKGDATADIR, "$PKGDATADIR")
|
2000-08-31 22:46:04 -07:00
|
|
|
if test "$GDB" != "no"; then
|
|
|
|
|
GDB_CMD_FILE="$PKGDATADIR/gdb.scr"
|
|
|
|
|
AC_DEFINE_UNQUOTED(GDB_CMD_FILE, "$GDB_CMD_FILE")
|
|
|
|
|
else
|
|
|
|
|
GDB_CMD_FILE=""
|
|
|
|
|
fi
|
|
|
|
|
AC_SUBST(GDB_CMD_FILE)
|
1999-08-17 18:12:47 -07:00
|
|
|
|
2000-08-31 22:46:04 -07:00
|
|
|
CPPFLAGS=`eval eval eval eval eval echo "-I$includedir -I$prefix/include $CPPFLAGS"`
|
2000-10-30 15:05:25 -08:00
|
|
|
CPPFLAGS=`echo $CPPFLAGS | tr ' ' '\n' | uniq | grep -v NONE | tr '\n' ' '`
|
1999-08-17 16:01:18 -07:00
|
|
|
CFLAGS=${CFLAGS--O}
|
2000-08-31 22:46:04 -07:00
|
|
|
LDFLAGS=`eval eval eval eval eval echo "-L$libdir -L$prefix/lib ${LDFLAGS--O}"`
|
2000-10-30 15:05:25 -08:00
|
|
|
LDFLAGS=`echo $LDFLAGS | tr ' ' '\n' | uniq | grep -v NONE | tr '\n' ' '`
|
2000-08-31 22:46:04 -07:00
|
|
|
LIBS="$GRLIBS $X_PRE_LIBS $LIBS $X_EXTRA_LIBS"
|
1999-08-17 16:01:18 -07:00
|
|
|
|
|
|
|
|
AC_SUBST(CC)
|
|
|
|
|
AC_SUBST(CFLAGS)
|
|
|
|
|
AC_SUBST(CPPFLAGS)
|
|
|
|
|
AC_SUBST(LDFLAGS)
|
|
|
|
|
AC_SUBST(LIBS)
|
|
|
|
|
AC_SUBST(THREADLIBS)
|
|
|
|
|
|
|
|
|
|
basedir=.
|
|
|
|
|
|
|
|
|
|
AM_CONFIG_HEADER(config.h)
|
|
|
|
|
|
2001-01-10 13:07:11 -08:00
|
|
|
AC_OUTPUT(Makefile bg/Makefile doc/Makefile utils/Makefile pix/Makefile
|
|
|
|
|
src/Makefile themes/Makefile Eterm.spec Eterm-mdk.spec)
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
|
|
|
|
|
# Mega evals to make sure all the relative variables get resolved.
|
|
|
|
|
BINDIR=`eval eval eval eval echo ${bindir}`
|
|
|
|
|
export BINDIR bindir prefix exec_prefix datadir PACKAGE
|
|
|
|
|
|
2000-08-31 22:46:04 -07:00
|
|
|
# The awk-fu below replaces @VAR@ in theme config files with the corresponding
|
|
|
|
|
# environment variables, kinda like AC_OUTPUT above.
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
changequote(%&, &%)dnl
|
|
|
|
|
%&
|
|
|
|
|
for i in utils/kEsetroot themes/Eterm/theme.cfg themes/auto/theme.cfg themes/cEterm/theme.cfg \
|
|
|
|
|
themes/chooser/theme.cfg themes/emacs/theme.cfg themes/irc/theme.cfg themes/mutt/theme.cfg \
|
|
|
|
|
themes/trans/theme.cfg ; do
|
|
|
|
|
echo creating $i
|
|
|
|
|
$AWK '{if (match($0,/@[A-Za-z0-9_]*@/)) {
|
|
|
|
|
i=ENVIRON[substr($0,RSTART+1,RLENGTH-2)];
|
|
|
|
|
outp=$0;
|
|
|
|
|
gsub(/@[A-Za-z0-9_]*@/,i,outp);
|
|
|
|
|
print outp;
|
|
|
|
|
} else {
|
|
|
|
|
print $0;
|
|
|
|
|
}
|
2000-12-29 14:59:13 -08:00
|
|
|
}' $srcdir/$i.in > $srcdir/$i
|
Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
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
2000-02-10 16:25:07 -08:00
|
|
|
done
|
|
|
|
|
&%
|
|
|
|
|
changequote([, ])dnl
|
1999-08-17 16:01:18 -07:00
|
|
|
|
|
|
|
|
dnl If we're not building with Imlib support, don't build Esetroot
|
1999-08-17 18:12:47 -07:00
|
|
|
if test -z "$GRLIBS"; then
|
2000-12-29 14:59:13 -08:00
|
|
|
sed -e 's/^bin_PROGRAMS.*$//g' $srcdir/doc/Makefile > $srcdir/doc/Makefile.new
|
|
|
|
|
mv $srcdir/doc/Makefile.new $srcdir/doc/Makefile
|
1999-08-17 16:01:18 -07:00
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
echo "
|
1999-08-17 18:12:47 -07:00
|
|
|
$PACKAGE $VERSION
|
1999-08-17 16:01:18 -07:00
|
|
|
Configuration:
|
1999-08-17 18:12:47 -07:00
|
|
|
--------------
|
1999-08-17 16:01:18 -07:00
|
|
|
|
2000-08-31 22:46:04 -07:00
|
|
|
Source code location: $srcdir
|
|
|
|
|
Host System Type: $host
|
|
|
|
|
Preprocessor: $CC $CPPFLAGS
|
|
|
|
|
Compiler: $CC $CFLAGS
|
|
|
|
|
Linker: $CC $LDFLAGS $LIBS
|
|
|
|
|
Install path: $prefix
|
1999-08-17 16:01:18 -07:00
|
|
|
|
1999-08-17 18:12:47 -07:00
|
|
|
See src/feature.h for further configuration information.
|
|
|
|
|
|
|
|
|
|
Now type 'make' to build $PACKAGE $VERSION.
|
|
|
|
|
"
|