From: Marcin Borkowski <mbork@mbork.pl>
To: Emanuel Berg <moasen@zoho.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: playing sounds from Emacs
Date: Tue, 15 Aug 2017 12:29:14 +0200 [thread overview]
Message-ID: <87pobxnmyt.fsf@jane> (raw)
In-Reply-To: <86shgtrf9d.fsf@zoho.com>
On 2017-08-14, at 23:49, Emanuel Berg <moasen@zoho.com> wrote:
>> (shell-command "omx-play-sound ~/bo/up.mp3")
>
> To use `shell-command' like that means
> everything halts until the command has been
> executed, which we can't have, but simply
> putting an "&" after - to make it
> "asynchronous" which is a nice way of saying
> the command will be executed in yet another
> shell, a subshell - that won't work. I get ugly
> output in buffer "*Async Shell Command*".
> and an error message:
>
> exited abnormally with code 1.
>
> Perhaps some shell color codes are, well,
> "async"! (So yes, in principle it should work.)
Dunno about the non-zero exit code, but did you see this:
http://mbork.pl/2016-04-07_Hiding_those_annoying_Async_Shell_Command_buffers
?
Also - for the record - this:
http://mbork.pl/2016-04-12_Showing_some_of_those_Async_Shell_Command_buffers
and that:
http://git.savannah.gnu.org/cgit/emacs.git/commit/etc/NEWS?id=85512e752191091d38cd5e34e7bed80eac1e9013
And also, `call-process-shell-command' and `shell-command-to-string'.
Hth,
--
Marcin Borkowski
prev parent reply other threads:[~2017-08-15 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 0:16 playing sounds from Emacs Emanuel Berg
2017-08-14 21:49 ` Emanuel Berg
2017-08-15 10:29 ` Marcin Borkowski [this message]
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=87pobxnmyt.fsf@jane \
--to=mbork@mbork.pl \
--cc=help-gnu-emacs@gnu.org \
--cc=moasen@zoho.com \
/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).