Re: How to avoid having shell scripts which fail from killing Emacs shell?

[David Karr]

On Jun 23, 6:15 am, "David M. Karr" <davidmichaelk...@gmail.com>
wrote:
> Pascal J. Bourguignon wrote:
> > David Karr <davidmichaelk...@gmail.com> writes:
>
> >> On Jun 20, 2:06 am, Peter Dyballa <Peter_Dyba...@Web.DE> wrote:
> >>> Am 20.06.2009 um 01:03 schrieb David Karr:
>
> >>>> to configure Emacs or the Bash inside Emacs, so that it doesn't get  
> >>>> killed when a script it's running fails.
> >>> Make the shell script trap (shell built-in) this catastrophic error  
> >>> and just execute an exit (shell built-in) instead (in last millennium  
> >>> this was standard). You can also run shell scripts asynchronously in  
> >>> a dedicated temporary buffer by executing it as a shell or compile  
> >>> command.
> >> If it matters, changing my test script to use "trap" to just exit on a
> >> signal didn't make any difference.
>
> > Probably your "script" is not a script but a text file containing
> > shell commands that you source.
>
> > The trick to avoid having it kill your shell, is to have it run in its
> > own shell (which it is free to kill).  To do so, you must put:
>
> > #!/bin/bash
>
> That's not the problem.  It's a proper script and executable.
>
> I've managed to find an element of this that seems to cause the problem,
> and removing that component makes it not happen.
>
> Currently, my test class also reads a line of input from stdin, in
> addition to some command-line arguments.  I tried creating a dummy test
> class that doesn't read from stdin, even when I force it to throw an
> exception, and that doesn't kill the shell.  However, when I then change
> the class to read a line from stdin, whether it throws an exception or
> not, the shell dies after the script completes.  I imagine I could
> simplify this test case by just doing the readline from the script,
> instead of the class.  I'll try that a little later this morning.

I didn't get a chance to run a test on Unix/Linux, but I tried
changing my script to just do a "read" with a prompt.  When I run
this, it does not kill the shell at the end of the script.  When I
change it back to do the same thing from Java, it kills the shell at
the end of the script.  Very odd.

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.