From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: What does code 123 mean?... (Shell command failed with code 123 and no output)
Date: Sat, 07 Jun 2008 09:45:50 +1000 [thread overview]
Message-ID: <87r6ba3z69.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.12730.1212734180.18990.help-gnu-emacs@gnu.org
Don Saklad <dsaklad@gnu.org> writes:
> a.
> What does code 123 mean?... in
>
> (Shell command failed with code 123 and no output)
>
This is usually the exit status from the shell command you are
running. Sometimes, programs that run commands will do a logical AND of
the return value from the command and some other value, which can be
used to indicate errors in executing the command rather than errors in
the comamnd itself and you will need to do a bit shift to get the actual
error code.
>
> b.
> Where is there a list of codes and what the codes mean?...
>
There isn't any standard list. There are some conventions on the use of
error codes, but many programs don't follow them. The best place to
check is probably the man page or other documentation for the command
you are running. Also, check the definition of shell-command - you can
call it with a 3rd argument that specifies a buffer for errors to be
sent to (i.e. shell commands stderr). Calling it with this set may give
you some clue as to what is going on.
HTH
Tim
--
tcross (at) rapttech dot com dot au
next prev parent reply other threads:[~2008-06-06 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12730.1212734180.18990.help-gnu-emacs@gnu.org>
2008-06-06 7:30 ` What does code 123 mean?... (Shell command failed with code 123 and no output) Xah
2008-06-06 23:45 ` Tim X [this message]
[not found] <mailman.12830.1212812278.18990.help-gnu-emacs@gnu.org>
2008-06-07 9:04 ` Johan Bockgård
2008-06-07 10:10 ` Peter Dyballa
2008-06-07 4:16 Don Saklad
-- strict thread matches above, loose matches on Subject: below --
2008-06-06 6:34 Don Saklad
2008-06-06 10:33 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r6ba3z69.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).