From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Peter Dyballa Newsgroups: gmane.emacs.help Subject: Re: How to avoid having shell scripts which fail from killing Emacs shell? Date: Tue, 23 Jun 2009 19:26:18 +0200 Message-ID: <32674A97-CDA2-41FF-8ACD-3018ABE8D291@Web.DE> References: <88ba12ed-8f02-4f3e-bb30-cc6155a38df2@f38g2000pra.googlegroups.com> <533b7087-5aa6-4278-b995-6a2166e7494e@c18g2000prh.googlegroups.com> <7cr5xbpbxz.fsf@pbourguignon.anevia.com> <40c8cb64-0eda-40d5-8d5a-547074c692de@q3g2000pra.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1245781962 23839 80.91.229.12 (23 Jun 2009 18:32:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Jun 2009 18:32:42 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: David Karr Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jun 23 20:32:35 2009 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 1MJAnJ-0003ml-Ra for geh-help-gnu-emacs@m.gmane.org; Tue, 23 Jun 2009 20:32:34 +0200 Original-Received: from localhost ([127.0.0.1]:43463 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJAnJ-0008Hq-1k for geh-help-gnu-emacs@m.gmane.org; Tue, 23 Jun 2009 14:32:33 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJ9lM-0005yF-39 for help-gnu-emacs@gnu.org; Tue, 23 Jun 2009 13:26:28 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJ9lG-0005vH-UE for help-gnu-emacs@gnu.org; Tue, 23 Jun 2009 13:26:27 -0400 Original-Received: from [199.232.76.173] (port=39607 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJ9lG-0005v4-NY for help-gnu-emacs@gnu.org; Tue, 23 Jun 2009 13:26:22 -0400 Original-Received: from fmmailgate01.web.de ([217.72.192.221]:33190) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJ9lG-0006YQ-7W for help-gnu-emacs@gnu.org; Tue, 23 Jun 2009 13:26:22 -0400 Original-Received: from smtp06.web.de (fmsmtp06.dlan.cinetic.de [172.20.5.172]) by fmmailgate01.web.de (Postfix) with ESMTP id D20C6106AA572; Tue, 23 Jun 2009 19:26:20 +0200 (CEST) Original-Received: from [91.35.230.120] (helo=[192.168.1.2]) by smtp06.web.de with asmtp (WEB.DE 4.110 #277) id 1MJ9lE-0002br-00; Tue, 23 Jun 2009 19:26:20 +0200 In-Reply-To: <40c8cb64-0eda-40d5-8d5a-547074c692de@q3g2000pra.googlegroups.com> X-Mailer: Apple Mail (2.753.1) X-Sender: Peter_Dyballa@web.de X-Provags-ID: V01U2FsdGVkX1+hrrGYnt0c4jQ7drA57R902ZwlPFhjRuRdTtJj cdOKPXV6b9PxPEPZIX3CoTbMZxJPz9Eivmsr/etkBmqzM4R24b WZkOiySr0z7v+D5RQstA== X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 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:65459 Archived-At: Am 23.06.2009 um 17:06 schrieb David Karr: > Note that I'm specifically stating "at the end of the script". If I > put a print statement in the script after the call to Java, it prints > the line, finishes the script, then kills the shell. Can you give us a sketch of your script, like: #!/bin/bash pushd # here the Java code starts with: # the Java function to read: ... # Here the Java code ends: # Final statement: ... Actual lines and line numbers (shell-command-on-region with pr -n - l9999) won't be bad. Maybe it's possible from seeing the code to see a design flaw or the actual cause ... Could be a log from your *shell* can provide further information. You can also invoke your script as bash -x ./script.name or put a line set -x near the beginning (line #2ff) into it to see bash execute the lines. This might give additional insight. -- Greetings Pete Upgraded, adj.: Didn't work the first time.