From: pjb@informatimago.com (Pascal J. Bourguignon)
To: help-gnu-emacs@gnu.org
Subject: Re: How to avoid having shell scripts which fail from killing Emacs shell?
Date: Tue, 23 Jun 2009 10:54:32 +0200 [thread overview]
Message-ID: <7cr5xbpbxz.fsf@pbourguignon.anevia.com> (raw)
In-Reply-To: 533b7087-5aa6-4278-b995-6a2166e7494e@c18g2000prh.googlegroups.com
David Karr <davidmichaelkarr@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
on the first line of the "script", and you should change the access
rights to give it executable rights:
chmod +x script
Then you can launch it as:
./script
instead of
. script # or source script
When you launch it like this, the kernel notice the #! characters at
the beginning of the file, and therefore forks a process running
/bin/bash, which will execute the rest of the script. When that
script exits or kills itself, it only kills the bash launched by the
kernel, and not the bash running in emacs.
--
__Pascal Bourguignon__
next prev parent reply other threads:[~2009-06-23 8:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 23:03 How to avoid having shell scripts which fail from killing Emacs shell? David Karr
2009-06-19 23:06 ` David Karr
2009-07-10 2:21 ` David Combs
2009-06-20 9:06 ` Peter Dyballa
[not found] ` <mailman.987.1245488796.2239.help-gnu-emacs@gnu.org>
2009-06-22 16:43 ` David Karr
2009-06-22 18:47 ` Peter Dyballa
2009-06-23 8:54 ` Pascal J. Bourguignon [this message]
2009-06-23 13:15 ` David M. Karr
2009-06-23 15:56 ` Peter Dyballa
[not found] ` <mailman.1141.1245762947.2239.help-gnu-emacs@gnu.org>
2009-06-23 15:06 ` David Karr
2009-06-23 17:26 ` Peter Dyballa
2009-06-22 20:21 ` David Karr
2009-06-22 22:49 ` Peter Dyballa
[not found] ` <mailman.1102.1245710994.2239.help-gnu-emacs@gnu.org>
2009-06-22 23:08 ` David Karr
2009-06-22 23:38 ` David Karr
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=7cr5xbpbxz.fsf@pbourguignon.anevia.com \
--to=pjb@informatimago.com \
--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).