From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How to communicate with a running external process with given PID?
Date: Sat, 20 Jul 2013 12:51:46 +0200 [thread overview]
Message-ID: <87r4et7bct.fsf@informatimago.com> (raw)
In-Reply-To: mailman.1456.1374311231.12400.help-gnu-emacs@gnu.org
Thorsten Jolitz <tjolitz@gmail.com> writes:
> Hi List,
>
> say I want to call another program (more exactly, another Lisp program
> that is not Emacs Lisp) from an Emacs Lisp program.
>
> My special requirement is that I don't want to start a new Emacs
> subprocess, but want to communicate with an existing (running) process.
> And there maybe several running instances of this program at the same
> time, so I want to communicate with one existing (running) process with
> a given PID.
>
> Now there is splendid support in Emacs for communicating with other
> programs, but always based on the assumption that Emacs starts and
> controls a new subprocess.
>
> There is chapter 37.12 "Accessing Other Processes" in the Elisp manual,
> and I can do successfully
>
> ,-------------------------
> | (process-attributes PID)
> `-------------------------
>
> to receive a lot of information about the process I want to communicate
> with.
>
> But what then? Where are the (e.g.) `process-send-string' or
> `process-send-region' functions for external processes I could use to
> communicate with my external program?
>
> I could run a server in the external lisp program and use a
> network-connection-object to send http-requests (e.g. with the help of
> emacs-request.el) via TCP - but that seems to be total overkill for my
> requirements.
>
> I just want to use a running external process with a given PID in a
> similar way I would use (a)synchronous processes created from Emacs with
> `call-process' or `start-process'. How can I do that?
>
> Maybe there is an obvious answer to this question that I don't see.
> Would be nice.
You need to read UNP.
http://www.unpbook.com/
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
You know you've been lisping too long when you see a recent picture of George
Lucas and think "Wait, I thought John McCarthy was dead!" -- Dalek_Baldwin
next parent reply other threads:[~2013-07-20 10:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1456.1374311231.12400.help-gnu-emacs@gnu.org>
2013-07-20 10:51 ` Pascal J. Bourguignon [this message]
2013-07-22 16:52 ` How to communicate with a running external process with given PID? Rustom Mody
2013-07-22 18:18 ` Pascal J. Bourguignon
2013-07-23 4:44 ` Rustom Mody
2013-07-20 10:52 ` Pascal J. Bourguignon
2013-07-20 11:57 ` Thorsten Jolitz
[not found] ` <mailman.1462.1374321447.12400.help-gnu-emacs@gnu.org>
2013-07-20 14:09 ` Pascal J. Bourguignon
2013-07-22 8:06 ` Thorsten Jolitz
2013-07-22 8:22 ` Aurélien Aptel
2013-07-22 9:43 ` Thorsten Jolitz
2013-07-22 14:15 ` Aurélien Aptel
2013-07-23 7:19 ` Thorsten Jolitz
[not found] ` <mailman.1547.1374486226.12400.help-gnu-emacs@gnu.org>
2013-07-22 18:14 ` Pascal J. Bourguignon
2013-07-20 9:06 Thorsten Jolitz
2013-07-22 13:02 ` Kevin Rodgers
2013-07-22 14:12 ` Thorsten Jolitz
2013-07-22 14:42 ` Aurélien Aptel
[not found] ` <mailman.1562.1374504168.12400.help-gnu-emacs@gnu.org>
2013-07-22 18:16 ` Pascal J. Bourguignon
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=87r4et7bct.fsf@informatimago.com \
--to=pjb@informatimago.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).