all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: phst@google.com, emacs-devel@gnu.org
Subject: Re: [PATCH] Add a module function to open a file descriptor connected to a pipe.
Date: Thu, 26 Mar 2020 21:00:21 +0200	[thread overview]
Message-ID: <83369v9c1m.fsf@gnu.org> (raw)
In-Reply-To: <20200326163021.111847-1-phst@google.com> (message from Philipp Stephani on Thu, 26 Mar 2020 17:30:21 +0100)

> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Thu, 26 Mar 2020 17:30:21 +0100
> Cc: Philipp Stephani <phst@google.com>
> 
> This patch implements a function that adapts an existing pipe
> process.  That way, users can use familiar tools like process filters
> or 'accept-process-output'.
> 
> * src/module-env-28.h: Add 'open_channel' module function.
> 
> * src/emacs-module.c (module_open_channel): Provide definition for
> 'open_channel'.
> (initialize_environment): Use it.
> 
> * src/process.c (open_channel_for_module): New helper function.
> (syms_of_process): Define necessary symbol.
> 
> * test/src/emacs-module-tests.el (module/async-pipe): New unit test.
> 
> * test/data/emacs-module/mod-test.c (signal_system_error): New helper
> function.
> (signal_errno): Use it.
> (write_to_pipe): New function running in the background.
> (Fmod_test_async_pipe): New test module function.
> (emacs_module_init): Export it.
> 
> * doc/lispref/internals.texi (Module Misc): Document new module
> function.
> 
> * doc/lispref/processes.texi (Asynchronous Processes): New anchor
> for pipe processes.

Thanks, but please also call out the change in NEWS.



  reply	other threads:[~2020-03-26 19:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 16:30 [PATCH] Add a module function to open a file descriptor connected to a pipe Philipp Stephani
2020-03-26 19:00 ` Eli Zaretskii [this message]
2020-03-26 20:51   ` Philipp Stephani

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83369v9c1m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=p.stephani2@gmail.com \
    --cc=phst@google.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.