From: Don Saklad <dsaklad@gnu.org>
To: help-gnu-emacs@gnu.org, dsaklad@gnu.org
Subject: Re: What does code 123 mean?... (Shell command failed with code 123 and no output)
Date: Sat, 07 Jun 2008 00:16:00 -0400 [thread overview]
Message-ID: <E1K4pqS-0005Bv-NT@fencepost.gnu.org> (raw)
> Which command was that? The interpretation of the code
> depends on the command which returned that code.
Around the web where are there examples of commands that could return
code 123 ?...
In this particular case it happened to be...
find -type f -print0 | xargs -0 grep -i strategylab
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
a.
What does code 123 mean?... in
(Shell command failed with code 123 and no output)
b.
Where is there a list of codes and what the codes mean?...
next reply other threads:[~2008-06-07 4:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 4:16 Don Saklad [this message]
[not found] <mailman.12830.1212812278.18990.help-gnu-emacs@gnu.org>
2008-06-07 9:04 ` What does code 123 mean?... (Shell command failed with code 123 and no output) Johan Bockgård
2008-06-07 10:10 ` Peter Dyballa
[not found] <mailman.12730.1212734180.18990.help-gnu-emacs@gnu.org>
2008-06-06 7:30 ` Xah
2008-06-06 23:45 ` Tim X
-- 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=E1K4pqS-0005Bv-NT@fencepost.gnu.org \
--to=dsaklad@gnu.org \
--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).