[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to avoid having shell scripts which fail from killing Emacs shel
From: |
Peter Dyballa |
Subject: |
Re: How to avoid having shell scripts which fail from killing Emacs shell? |
Date: |
Tue, 23 Jun 2009 19:26:18 +0200 |
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
<some variable settings>
pushd <some working directory>
# here the Java code starts with:
<a cup of hot Java?>
# the Java function to read:
...
# Here the Java code ends:
<code>
<shell code>
# Final statement:
...
<shell script ends here with a newline>
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.
Re: How to avoid having shell scripts which fail from killing Emacs shell?, David Karr, 2009/06/22
Message not available