unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <kernel-hacker@bennee.com>
To: GNU Emacs users list <help-gnu-emacs@gnu.org>
Subject: stdio access to the Emacs REPL
Date: Mon, 11 Nov 2013 11:40:32 +0000	[thread overview]
Message-ID: <p1txfj5fpr.fsf@linaro.org> (raw)

Hi,

I'm looking at replacing/augmenting the current xmlrpc method used by
Edit with Emacs on Chrome to communicate with the edit-server.
Chrome(ium) now provides a new native message API which offers a simpler
stdio based access:

http://developer.chrome.com/extensions/messaging.html#native-messaging

I was wondering if there is anyway to hook a line based stdio link into
a running emacs session. Something like:

emacsclient -t -e "(eshell)"

But without any of the extra display gubbins. All I want is something
that I can write an sexp to and then process the response on stdout.

Any ideas?

-- 
Alex Bennée




             reply	other threads:[~2013-11-11 11:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 11:40 Alex Bennée [this message]
2013-11-11 13:45 ` stdio access to the Emacs REPL Thorsten Jolitz
2013-11-15  9:04   ` Alex Bennée

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=p1txfj5fpr.fsf@linaro.org \
    --to=kernel-hacker@bennee.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).