eshell: bug in Makefile?

eshell: bug in Makefile?

Post by Christian Lembur » Tue, 12 Nov 2002 21:52:48

On an (admittedly old) XEmacs version '21.1 (patch 12) "Channel
Islands" XEmacs Lucid', eshell would, during compilation, write
useless eshell-auto.el and pcomplete-auto.el files, which resulted in
pcomplete and eshell not being available after loading the above

The problem was fixed by exchanging the order of arguments in the call
that generated the above files in the Makefile, after examining
(describe-function 'batch-update-autoloads).

This is probably not a big problem nowadays that eshell is distributed
with XEmacs, but it might save somebody else out there some time.

--- eshell-2.4.2/Makefile       Fri Oct 13 12:49:59 2000

 infodir = $(prefix)/info
 docdir = $(prefix)/doc

-EMACS   = emacs
+EMACS   = xemacs
 MAKEINFO = makeinfo
 TEXI2DVI = texi2dvi

        echo ";;; DO NOT MODIFY THIS FILE" > eshell-auto.el
        echo "(if (featurep 'eshell-auto) (error \"Already loaded\"))" \
                >> eshell-auto.el
-       $(BEMACS) -f eshell-generate-autoloads ./eshell-auto.el .
+       $(BEMACS) -f eshell-generate-autoloads . ./eshell-auto.el
        echo "(provide 'eshell-auto)" >> eshell-auto.el
        ln -f eshell-auto.el auto-autoloads.el

--- pcomplete-1.1.7/Makefile    Thu Apr 27 11:49:54 2000

 infodir = $(prefix)/info
 docdir = $(prefix)/doc

-EMACS  = emacs
+EMACS  = xemacs
 MAKEINFO= makeinfo
 TEXI2DVI= texi2dvi

        echo ";;; DO NOT MODIFY THIS FILE" > pcmpl-auto.el
        echo "(if (featurep 'pcmpl-auto) (error \"Already loaded\"))" \
                >> pcmpl-auto.el
-       $(BEMACS) -f pcomplete-generate-autoloads ./pcmpl-auto.el .
+       $(BEMACS) -f pcomplete-generate-autoloads . ./pcmpl-auto.el
        echo "(provide 'pcmpl-auto)" >> pcmpl-auto.el
        ln pcmpl-auto.el auto-autoloads.el


 "Calvin Coolidge looks as if he had been weaned on a pickle."
                -- Alice Roosevelt Longworth


1. eshell: eshell-command-result and environment


It would be useful if 'eshell-command-result' inherited the set of
environment variables from the invoking shell, since this would make
it more convenient to write eshell functions.

Consider the following example: a function that invokes snmpget on a
remote machine, whose hostname is passed as an argument. The snmpget
command uses an environment variable MIBS; even if this is set (using
"export MIBS=/path/to/the/mib") in the eshell session, it isn't
propagated to the snmp-uptime command.

Is there is a better way to run external commands?  The following
example is simplified; I really want to do a regexp search on the
results of snmpget.

(defun eshell/snmp-uptime (&rest args)
   (format "snmpget %s public cpuUpTime.0" (first args))))

[I know about the -m option to snmpget]

Eric Marsden                          <URL:>

2. Whole house noise filter??

3. Eshell-buffer-shorthand and Eshell completions

4. Can't access DBXG50 with MIDI keyboard

5. eshell/rm bug?

6. 4,5 - 5 m/s

7. bug?????xemacs and Makefiles

8. makefile-mode syntax highlighting bug?

9. dtx and ins in xemacs

10. Adding C-code plug-ins to Emacs?

11. EMACS/AUCTEX and dtx/ins file types

12. Adding C-code plug-ins to Emacs?