Akim> Now, there's a README-alpha which is rather explicit.

Martin> Did you know that this autoconf uses $SHELL instead of
Martin> ${CONFIG_SHELL-/bin/sh}?

Akim> Where?

(martin@wobble) /usr/share/autoconf $ g -w SHELL acgeneral.m4 
acgeneral.m4:211:SHELL=${CONFIG_SHELL-/bin/sh}
acgeneral.m4:699:AC_SUBST(SHELL)dnl
acgeneral.m4:876:ac_config_guess="$SHELL $ac_aux_dir/config.guess"
acgeneral.m4:877:ac_config_sub="$SHELL $ac_aux_dir/config.sub"
acgeneral.m4:878:ac_configure="$SHELL $ac_aux_dir/configure" # This should be Cygnus 
configure.
acgeneral.m4:2135:test "$no_create" = yes || $SHELL $CONFIG_STATUS || exit 1
acgeneral.m4:2552:      ac_sub_configure="$SHELL $ac_sub_srcdir/configure"

I see. That original SHELL=${CONFIG_SHELL-/bin/sh} is in
AC_INIT_PARSE_ARGS.  Naturally I redefine that...  OK, this is the
price we have to pay.

I'll just redefine AC_PREREQ(2.13) to be a == test, not a <= test.

Martin> This would fail in the most obvious way if the user's shell
Martin> was, say csh (untested).

Martin> My own SHELL is /bin/zsh, 

Akim> I've always thought that peopling thinking and feeling like XEmacs
Akim> *must* run zsh.  Seems like I was right :)

Every XEmacs developer is completely different.

The one feature I couldn't switch shells for is the autocd feature.
If I type the name of a directory, I want to go there - what else can
you do with a directory?

Martin

Reply via email to