[Top][All Lists]

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

Testing the return value of call-process

From: Jesper Harder
Subject: Testing the return value of call-process
Date: Sun, 07 Dec 2003 19:25:45 +0100
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)

In GNU Emacs (i686-pc-linux-gnu, GTK+ Version 2.0.2)

The return value of `call-process' can be a number or a string.  This
means that `=' or `zerop' shouldn't be used to test it, because it
will result in an error if the value happens to be a string.

Below is a patch that fixes some cases.

2003-12-07  Jesper Harder  <address@hidden>

        * progmodes/idlwave.el (idlwave-make-tags): Don't use = or zerop
        to test the return value of call-process, because it can be a

        * textmodes/flyspell.el (flyspell-large-region): do.

        * progmodes/make-mode.el (makefile-query-by-make-minus-q): do.

        * emulation/viper-util.el (viper-glob-unix-files): do.

        * emacs-lisp/shadow.el (shadow-same-file-or-nonexistent): do.

        * man.el (Man-init-defvars): do.

        * jka-compr.el (jka-compr-call-process): do.

        * files.el (get-free-disk-space,insert-directory): do.

        * ediff-ptch.el (ediff-test-patch-utility): do.

        * ediff-diff.el (ediff-test-utility): do.

        * dired-aux.el (dired-check-process): do.

        * mail/sendmail.el (sendmail-send-it): do.

Attachment: callproc.diff
Description: Text Data

reply via email to

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