From: Sam Halliday <sam.halliday@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: run emacs in batch mode without a tty
Date: Fri, 3 Jul 2015 16:56:05 -0700 (PDT) [thread overview]
Message-ID: <86bcdf0f-6c79-4d20-8eb6-ca0f455fa78e@googlegroups.com> (raw)
In-Reply-To: <barmar-022B57.18552603072015@88-209-239-213.giganet.hu>
Hi Barry, you might want to read my other responses. Yes it is possible to do what I need.
On Friday, 3 July 2015 23:55:29 UTC+1, Barry Margolin wrote:
> In article <ac8061d2-9984-4ef1-9199-51e47d5c7439@googlegroups.com>,
> Sam Halliday <sam.halliday@gmail.com> wrote:
>
> > Aha! It would appear that when emacs is started in -batch mode then the
> > program exits when it runs through the initial script.
> >
> > But my tests are starting up a process, attaching a sentinel and then
> > reacting to some triggers in that file. Under non-batch mode, emacs stays
> > open until I call `kill-emacs`... but *now* it's dying too early.
> >
> > So my question then becomes: is there a way to stop emacs -batch from
> > terminating when it reaches the end of the script? i.e. require an explicit
> > kill-emacs call.
>
> I don't think so.
>
> In normal Emacs, when the script finishes, it goes to the main input
> loop, which displays the buffer and processes terminal input. That's why
> it needs a terminal.
>
> In batch mode, there's no terminal or redisplay, so there's no main
> input loop. It just runs the script and exits.
>
> Running another process isn't compatible with this mode, because
> processing the process output is also part of that main input loop.
>
> --
> Barry Margolin, barmar@alum.mit.edu
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***
next prev parent reply other threads:[~2015-07-03 23:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 9:14 run emacs in batch mode without a tty Sam Halliday
2015-07-03 10:26 ` tomas
[not found] ` <mailman.6225.1435919180.904.help-gnu-emacs@gnu.org>
2015-07-03 10:28 ` Sam Halliday
2015-07-03 10:45 ` tomas
[not found] ` <mailman.6226.1435920329.904.help-gnu-emacs@gnu.org>
2015-07-03 13:27 ` Sam Halliday
2015-07-04 8:30 ` tomas
2015-07-03 12:00 ` Eli Zaretskii
[not found] ` <mailman.6230.1435924859.904.help-gnu-emacs@gnu.org>
2015-07-03 13:26 ` Sam Halliday
2015-07-03 13:51 ` Eli Zaretskii
2015-07-04 6:56 ` Steinar Bang
2015-07-04 7:32 ` Eli Zaretskii
[not found] ` <mailman.6240.1435931463.904.help-gnu-emacs@gnu.org>
2015-07-03 15:07 ` Barry Margolin
2015-07-03 17:48 ` Eli Zaretskii
2015-07-03 20:13 ` Emanuel Berg
2015-07-03 15:42 ` Sam Halliday
2015-07-03 16:29 ` Sam Halliday
2015-07-03 17:51 ` Eli Zaretskii
2015-07-03 17:07 ` Sam Halliday
2015-07-03 20:14 ` Eli Zaretskii
[not found] ` <mailman.6254.1435954474.904.help-gnu-emacs@gnu.org>
2015-07-03 20:43 ` Sam Halliday
2015-07-03 21:25 ` Sam Halliday
2015-07-03 21:52 ` Sam Halliday
2015-07-03 22:01 ` Sam Halliday
2015-07-04 7:42 ` Eli Zaretskii
2015-07-03 22:55 ` Barry Margolin
2015-07-03 23:56 ` Sam Halliday [this message]
2015-07-04 7:37 ` Eli Zaretskii
2015-07-04 7:44 ` Eli Zaretskii
2015-07-04 7:45 ` Eli Zaretskii
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=86bcdf0f-6c79-4d20-8eb6-ca0f455fa78e@googlegroups.com \
--to=sam.halliday@gmail.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).