all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Beyond release
Date: Mon, 27 Jun 2016 17:40:56 +0100	[thread overview]
Message-ID: <878txqfuuf.fsf@russet.org.uk> (raw)
In-Reply-To: <57714BA1.8030506@gmail.com> ("Clément Pit--Claudel"'s message of "Mon, 27 Jun 2016 11:52:01 -0400")

Clément Pit--Claudel <clement.pit@gmail.com> writes:

> On 2016-06-27 11:33, Andreas Röhler wrote:
>>> I think that's an incorrect characterisation (see statements that
>>> Makarius made on the Proof General mailing list).
>> 
>> That's where my conclusions are from. Any precise spot to tell
>> otherwise?
>
> Yes: Makarius wrote: "While it is technically feasible to connect Proof
> General to Isabelle/Scala/PIDE in some imitation of the old TTY mode, I
> personally don't believe that there are serious adherents to Emacs still
> around to do that."


I'm guessing that Isabelle/Emacs integration used "parsing output"
interaction. FWIW, I think that the days of this form of archictecture
are numbered. Both scala and clojure interaction now use something with
a structured protocol, with a specialized server on the scala or clojure
side. A similar thing is happening with R, also, and maybe with JDEE.

I don't know if anything could be done, but adding general support for
repl interaction to core or ELPA would probably be a good thing. I don't
know if it is possible -- most of the tools that I have mentioned so far
use different protocols, so perhaps it is not.


>> That's interesting. Maybe that would also worth being reflected. So
>> extending in Java should be easier than in Emacs Lisp? How could it
>> came to this?
>
> Does Makarius know Emacs Lisp?

Which is the problem. You don't need to ask if he knows Java, because
everyone knows Java.

Phil



  parent reply	other threads:[~2016-06-27 16:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27  9:58 Beyond release Andreas Röhler
2016-06-27 14:18 ` Clément Pit--Claudel
2016-06-27 15:33   ` Andreas Röhler
2016-06-27 15:52     ` Clément Pit--Claudel
2016-06-27 16:10       ` Dmitry Gutov
2016-06-27 16:25         ` Andreas Röhler
2016-06-27 16:55           ` Dmitry Gutov
2016-06-27 18:10             ` Andreas Röhler
2016-06-27 19:55               ` Dmitry Gutov
2016-06-28  6:14                 ` Andreas Röhler
2016-06-28 11:13                   ` Dmitry Gutov
2016-06-27 20:29               ` Alan Mackenzie
2016-06-28  8:39                 ` Andreas Röhler
2016-06-27 16:21       ` Andreas Röhler
2016-06-27 16:40       ` Phillip Lord [this message]
2016-06-27 18:00         ` Clément Pit--Claudel
2016-06-27 18:05         ` Clément Pit--Claudel
2016-06-27 20:35           ` Phillip Lord
2016-06-27 15:53     ` Clément Pit--Claudel

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=878txqfuuf.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=clement.pit@gmail.com \
    --cc=emacs-devel@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.
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.