From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tim X Newsgroups: gmane.emacs.help 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 Organization: Rapt Technologies Message-ID: <87r6ba3z69.fsf@lion.rapttech.com.au> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1212799251 4186 80.91.229.12 (7 Jun 2008 00:40:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 7 Jun 2008 00:40:51 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jun 07 02:41:34 2008 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K4mUo-0002Mv-5u for geh-help-gnu-emacs@m.gmane.org; Sat, 07 Jun 2008 02:41:26 +0200 Original-Received: from localhost ([127.0.0.1]:55021 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K4mU1-0003Bj-5l for geh-help-gnu-emacs@m.gmane.org; Fri, 06 Jun 2008 20:40:37 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!news1.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local02.nntp.dca.giganews.com!nntp.posted.internode!news.posted.internode.POSTED!not-for-mail Original-NNTP-Posting-Date: Fri, 06 Jun 2008 18:45:51 -0500 Original-Newsgroups: gnu.emacs.help User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:4nLHmCCPUAkEWBZarDUM7zGD3/g= Original-Lines: 36 X-Usenet-Provider: http://www.giganews.com Original-NNTP-Posting-Host: 121.44.99.74 Original-X-Trace: sv3-988hnswq2jSZ+h+pK/PTC5Skdmoxgac9P8Q5WjAIv8nbYui1VRI5io50M3QVxfoFMJtH6LmanCaIGM6!q9b/IYDzderv5kYfEiE4InYdIv/sFJi5FYdFZYG3mgJBB4nvhNTGbKtqC7jR2lGY6bCepdcl X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.39 Original-Xref: news.stanford.edu gnu.emacs.help:159204 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:54562 Archived-At: Don Saklad 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