From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Cross Subject: Re: ob-clojure.el is not compatible with new CIDER API Date: Tue, 24 Jul 2018 16:54:30 +1000 Message-ID: References: <877elva0qj.fsf@gmail.com> <87tvoww51l.fsf@gmail.com> <87efftp83f.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000008484130571b93c2f" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35639) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fhrDY-0005zb-46 for emacs-orgmode@gnu.org; Tue, 24 Jul 2018 02:54:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fhrDW-00069T-Uc for emacs-orgmode@gnu.org; Tue, 24 Jul 2018 02:54:44 -0400 Received: from mail-oi0-x22a.google.com ([2607:f8b0:4003:c06::22a]:33420) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fhrDW-00068K-O1 for emacs-orgmode@gnu.org; Tue, 24 Jul 2018 02:54:42 -0400 Received: by mail-oi0-x22a.google.com with SMTP id l10-v6so5684154oii.0 for ; Mon, 23 Jul 2018 23:54:42 -0700 (PDT) In-Reply-To: <87efftp83f.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: =?UTF-8?B?6LevUmljYXJkbyBNLg==?= Cc: Org-mode --0000000000008484130571b93c2f Content-Type: text/plain; charset="UTF-8" I did begin to look at it. From memory, the inf-clojure integration didn't look that hard, but it did require some additional scaffolding to mae the comms work well. I then got distracted with a new job and haven't had time to go back to it. Currently, I've not had time to do any Clojure work, so it is not high on the priority list. On Tue, 24 Jul 2018 at 15:09, stardiviner wrote: > > Tim Cross writes: > > > I did this a couple of times in the past, but not long afterwards, CIDER > > would again change and the interface would no longer work. > > > > Personally, I'm not convinced that using CIDER actually provides much > > advantage at this time due to how rapidly it is evolving. Org would > > likely do better just having an interface based around a simple > > interface, such a inf-clojure. > > > > Hi, Tim, I checked "inf-clojure", you're right, ob-clojure should migrate > to inf-clojure. it is more stable and more suitable for ob-clojure. Have > you tried this before? > > -- > [ stardiviner ] don't need to convince with trends. > Blog: https://stardiviner.github.io/ > IRC(freenode): stardiviner > GPG: F09F650D7D674819892591401B5DF1C95AE89AC3 > > > -- regards, Tim -- Tim Cross --0000000000008484130571b93c2f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I did begin to look at it. From memory, the inf-clojure in= tegration didn't look that hard, but it did require some additional sca= ffolding to mae the comms work well. I then got distracted with a new job a= nd haven't had time to go back to it. Currently, I've not had time = to do any Clojure work, so it is not high on the priority list.

=C2=A0

O= n Tue, 24 Jul 2018 at 15:09, stardiviner <numbchild@gmail.com> wrote:

Tim Cross <th= eophilusx@gmail.com> writes:

> I did this a couple of times in the past, but not long afterwards, CID= ER
> would again change and the interface would no longer work.
>
> Personally, I'm not convinced that using CIDER actually provides m= uch
> advantage at this time due to how rapidly it is evolving. Org would > likely do better just having an interface based around a simple
> interface, such a inf-clojure.
>

Hi, Tim, I checked "inf-clojure", you're right, ob-clojure sh= ould migrate to inf-clojure. it is more stable and more suitable for ob-clo= jure. Have you tried this before?

--
[ stardiviner ] don't need to convince with trends.
=C2=A0 =C2=A0 =C2=A0 =C2=A0Blog: https://stardiviner.github.io/ =C2=A0 =C2=A0 =C2=A0 =C2=A0IRC(freenode): stardiviner
=C2=A0 =C2=A0 =C2=A0 =C2=A0GPG: F09F650D7D674819892591401B5DF1C95AE89AC3



--
regards,

Tim

--<= /div>Tim Cross

--0000000000008484130571b93c2f--