unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Nicolas Graner <nicolas@graner.name>
Cc: help-gnu-emacs@gnu.org
Subject: Re: sending data to an asynchronous process
Date: Fri, 2 Apr 2021 21:54:02 +0300	[thread overview]
Message-ID: <YGdoSlGfxISG6JSx@protected.localdomain> (raw)
In-Reply-To: <86im548rg5.fsf@graner.name>

* Nicolas Graner <nicolas@graner.name> [2021-04-02 21:37]:
> Jean Louis <bugs@gnu.support> wrote on 2021-04-02 20:18:
> > * Nicolas Graner <nicolas@graner.name> [2021-04-02 13:21]:
> >> I am writing a program that creates audio samples in an emacs
> >> buffer, then sends them to an external program (sox) to play in
> >> the background while I continue working with emacs. Part of the
> >> code is roughly as follows:
> >> 
> > (setq process
> >       (let ((process-connection-type nil))
> > 	(start-process "my-process" nil
> > 		       "sox" "-r" rate "-c" channels "-b" bits "-e" encoding "-q" "-d")))
> > (process-send-region process start end)
> > (process-send-eof process)
> >
> > For process-send-region, it says:
> >
> > If PROCESS is a non-blocking network process that hasn’t been fully
> > set up yet, this function will block until socket setup has completed.
> >
> > Maybe that applies.

(defun rcd-command-output-from-input (program input &rest args)
  "Returns output from PROGRAM INPUT with optional ARGS"
  (let* ((output (with-temp-buffer
		  (insert input)
		  (apply #'call-process-region nil nil program t t nil args)
		  (buffer-string))))
    output))

(rcd-command-output-from-input "sox" (buffer-string)
			       "-r" "44100"
			       "-c" "2"
			       "-b" "32"
			       "-e" "signed-integer"
			       "-t" "raw"
			       "-"
			       "-q"
			       "-d") → ""

I have tried this above, it plays my buffer. But it is not
asynchronous.

There is library async.el, but I am not sure if it can receive from
buffer directly, you can however, make your function to feed the
buffer first into a file.

async-start-process is an autoloaded compiled Lisp function in
‘async.el’.

(async-start-process NAME PROGRAM FINISH-FUNC &rest PROGRAM-ARGS)

Start the executable PROGRAM asynchronously named NAME.  See ‘async-start’.
PROGRAM is passed PROGRAM-ARGS, calling FINISH-FUNC with the
process object when done.  If FINISH-FUNC is nil, the future
object will return the process object when the program is
finished.  Set DEFAULT-DIRECTORY to change PROGRAM’s current
working directory.

async-send is a compiled Lisp function in ‘async.el’.

(async-send &rest ARGS)

Send the given messages to the asychronous Emacs PROCESS.


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

Sign an open letter in support of Richard M. Stallman
https://rms-support-letter.github.io/




  reply	other threads:[~2021-04-02 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02 10:20 sending data to an asynchronous process Nicolas Graner
2021-04-02 16:13 ` Jean Louis
2021-04-02 17:18 ` Jean Louis
2021-04-02 18:35   ` Nicolas Graner
2021-04-02 18:54     ` Jean Louis [this message]
2021-04-02 19:10       ` Jean Louis
2021-04-02 19:15 ` Eli Zaretskii
2021-04-02 23:03   ` Nicolas Graner

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=YGdoSlGfxISG6JSx@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --cc=nicolas@graner.name \
    /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).