From: Hilary <hils@newearth.demon.co.uk.invalid>
To: help-gnu-emacs@gnu.org
Subject: Spawning autonomous shell commands
Date: Thu, 27 Sep 2012 22:00:59 +0100 [thread overview]
Message-ID: <k42eq7$b4p$1@speranza.aioe.org> (raw)
This may be partly a windoze question. I use this on a windoze box:
(defun espeak-region ()
"Send the region to espeak"
(interactive)
(shell-command-on-region (region-beginning) (region-end) "espeak -v
mb-en1 -p 50 -s 150 --stdin ")
)
It works, but it locks up emacs until espeak has finished reading the
text. Is there a way of spawning espeak as an autonomous process which
can finish in its own time?
--
Hilary S
next reply other threads:[~2012-09-27 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 21:00 Hilary [this message]
2012-09-28 7:06 ` Spawning autonomous shell commands Eli Zaretskii
[not found] ` <mailman.9895.1348816018.855.help-gnu-emacs@gnu.org>
2012-09-28 17:49 ` Hilary
2012-09-28 19:17 ` 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='k42eq7$b4p$1@speranza.aioe.org' \
--to=hils@newearth.demon.co.uk.invalid \
--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).