Throwing error if process started with call-process returns error exit code

Throwing error if process started with call-process returns error exit code

[Kaushal Modi]

Hello,

What's the canonical way to check if the process initiated using
call-process failed?

From the signature of this function:

  (call-process PROGRAM &optional INFILE DESTINATION DISPLAY &rest ARGS)

, I can manually parse the buffer I set as DESTINATION and look for errors
like "Unknown option" etc.. but that would be too specific to the process I
am running.

So I was wondering if there's a wrapper function I can use readily, or
something that simply tells me if the process passed or failed.

In case of error, I'd like that parent Elisp function to stop further
execution and throw a user-error.
-- 

Kaushal Modi

Re: Throwing error if process started with call-process returns error exit code

[Eli Zaretskii]

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Thu, 19 Jul 2018 13:39:55 -0400
> 
> What's the canonical way to check if the process initiated using
> call-process failed?

The usual method is to examine the return value of call-process.

Re: Throwing error if process started with call-process returns error exit code

[Kaushal Modi]

Ah yes. Thanks!

I missed reading that in doc-string the first time. That works.

If the return code is not 0, I then just ask the user to see the process
buffer.

On Thu, Jul 19, 2018 at 1:44 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > What's the canonical way to check if the process initiated using
> > call-process failed?
>
> The usual method is to examine the return value of call-process.
>
-- 

Kaushal Modi