From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Jorgen Schaefer <forcer@forcix.cx>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Is intellisense features integration in Emacs technically possible?
Date: Fri, 24 Jan 2014 11:58:45 +0000 [thread overview]
Message-ID: <87sisd7fre.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <20140123215656.30bf63b8@forcix.kollektiv-hamburg.de> (Jorgen Schaefer's message of "Thu, 23 Jan 2014 21:56:56 +0100")
Jorgen Schaefer <forcer@forcix.cx> writes:
> On Thu, 23 Jan 2014 10:12:44 -0500
> Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
>> >> It's mainly a common interface for such external programs so that
>> >> we can add more languages more easily. The current effort of
>> >> unifying the completion interface as well as supporting company
>> >> mode as a front-end is going a great deal forward in that.
>> > I'm not convinced that a single interface would work; again, using
>> > clojure as example, this has moved away from a single interface in
>> > Emacs (i.e. slime/swank) and toward a single interface for Clojure
>> > (so that the Clojure side offers a single server, for different
>> > editors).
>>
>
> On the topic of a "unified RPC interface", it does grate me a bit that
> every mode implements its own RPC with a major language (elpy
> implements a simple JSON-RPC one, emacs-jedi uses the elaborate EPC
> library, ropemacs uses Pymacs which uses a very idiosyncratic protocol,
> slime does the swank stuff, clojure apparently has its own API now,
> etc. etc.), but I'm not sure if that's a solvable problem.
This is the sort of thing I was talking about when I said "I'm not
convinced a single interface would work".
> Choice of the RPC mechanism depends as much on Emacs as it does on the
> capabilities of the language being talked to. The JSON-RPC code in
> elpy is a total of 450 lines, both the Emacs Lisp as well as the
> Python side, including docstrings and comments, so not having a
> standard one is not really a huge problem.
But that the mechanism is an RPC, I think, is more or less a given.
Having a set of standard call-back functions for instance would help. If
they all used the same interface, then you could chain them together and
compose them in a sane way. So, for instance, you might be able to pick
up an "parse a JSON-RPC into lisp datastructures" callback, an "adapt
the lisp data structures from my library", and a "do a completion
callback", then compose them and use them. The first could be generic
for a given syntax family of RPC calls, the last generic for the
functionality. So you'd only need to write the middle bit for a given
language.
Just a thought.
Phil
next prev parent reply other threads:[~2014-01-24 11:58 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 2:01 Is intellisense features integration in Emacs technically possible? Jorge Araya Navarro
2014-01-21 18:59 ` Tom
2014-01-21 19:29 ` Eli Zaretskii
2014-01-21 19:58 ` Tom
2014-01-22 3:53 ` Eli Zaretskii
2014-01-22 4:36 ` Óscar Fuentes
2014-01-22 6:31 ` David Kastrup
2014-01-22 7:26 ` Stephen J. Turnbull
2014-01-22 8:13 ` David Kastrup
2014-01-22 9:33 ` Stephen J. Turnbull
2014-01-22 11:02 ` David Kastrup
2014-01-22 13:35 ` Stefan Monnier
2014-01-22 16:04 ` Eli Zaretskii
2014-01-23 8:13 ` Stephen J. Turnbull
2014-01-23 8:44 ` David Kastrup
2014-01-23 16:19 ` Eli Zaretskii
2014-01-24 2:57 ` Stephen J. Turnbull
2014-01-24 7:43 ` Eli Zaretskii
2014-01-22 8:49 ` Rüdiger Sonderfeld
2014-01-22 11:53 ` Óscar Fuentes
2014-01-22 15:56 ` Eli Zaretskii
2014-01-22 18:46 ` Stefan Monnier
2014-01-22 19:10 ` David Engster
2014-01-22 16:52 ` David Engster
2014-01-22 15:59 ` Eli Zaretskii
2014-01-22 16:41 ` David Engster
2014-01-22 17:16 ` Dmitry Gutov
2014-01-22 17:36 ` David Engster
2014-01-22 18:12 ` Óscar Fuentes
2014-01-22 18:34 ` David Engster
2014-01-21 20:03 ` Andreas Röhler
2014-01-22 3:54 ` Eli Zaretskii
2014-01-22 6:28 ` Stephen J. Turnbull
2014-01-22 16:03 ` Eli Zaretskii
2014-01-23 7:54 ` Stephen J. Turnbull
2014-01-22 17:29 ` Phillip Lord
2014-01-22 18:49 ` Jorgen Schaefer
2014-01-23 9:00 ` Andreas Röhler
2014-01-23 19:34 ` Jorgen Schaefer
2014-01-23 13:20 ` Phillip Lord
2014-01-23 15:12 ` Stefan Monnier
2014-01-23 20:56 ` Jorgen Schaefer
2014-01-23 22:13 ` Stefan Monnier
2014-01-23 22:43 ` Jorgen Schaefer
2014-01-24 1:40 ` Stefan Monnier
2014-01-24 10:25 ` Jorgen Schaefer
2014-01-24 12:46 ` Thien-Thi Nguyen
2014-01-24 13:20 ` Stefan Monnier
2014-01-25 23:42 ` Dmitry Gutov
2014-01-24 11:58 ` Phillip Lord [this message]
2014-01-25 23:53 ` Dmitry Gutov
2014-01-26 10:15 ` Jorgen Schaefer
2014-01-26 23:04 ` Dmitry Gutov
2014-01-23 2:22 ` Eric M. Ludlam
2014-01-23 13:26 ` Phillip Lord
2014-01-21 19:53 ` David Engster
2014-01-21 20:07 ` Tom
2014-01-21 20:13 ` David Engster
2014-01-21 20:24 ` Tom
2014-01-21 22:50 ` David Engster
2014-01-22 3:55 ` Eli Zaretskii
2014-01-23 9:16 ` Andreas Röhler
2014-01-23 17:17 ` Richard Stallman
[not found] <mailman.172802.1390363342.10747.emacs-devel@gnu.org>
2014-01-22 7:39 ` Jorge Araya Navarro
2014-01-22 15:39 ` Eli Zaretskii
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=87sisd7fre.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--cc=emacs-devel@gnu.org \
--cc=forcer@forcix.cx \
--cc=monnier@iro.umontreal.ca \
/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.