[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs Shell mode vs AC_CHECK_PROG(EMACS, ...)

From: Don.Bashford
Subject: Re: emacs Shell mode vs AC_CHECK_PROG(EMACS, ...)
Date: Mon, 11 Sep 2006 16:40:51 -0500
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (Sanjō) APEL/10.6 Emacs/21.3 (i386-redhat-linux-gnu) MULE/5.0 (SAKAKI)

>>>>> "Chet" == Chet Ramey <address@hidden> writes:

    Chet> Bash does inspect the EMACS environment variable as part of
    Chet> checking whether or not to turn off line editing even when
    Chet> the shell is interactive.  It also checks for TERM==emacs.
    Chet> If the shell discovers it's running in an emacs buffer, it
    Chet> turns off readline.

Maybe emacs should be in charge of turning readline off directly
instead expecting the shell to check envars to deal with special
cases.  For example, emacs could send the shell something like "shopt
-u -o emacs; shopt -u -o vi".  Then emacs could leave EMACS alone.

It might also be a good idea for AC_CHECK_COMMAND to at least give a
warning if shell variables have crazy-seeming values like "t", "0" or
"1".  Better yet, when envars try to override command names it could
check whether the the command really exists.  Or,

  PROG=enval AC_CHECK_COMMAND(PROG, foo bar ...) 
         --> AC_CHECK_COMMAND(PROG, enval foo bar ...) 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]