From: Tim Cross <theophilusx@gmail.com>
To: "路Ricardo M." <numbchild@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: ob-clojure.el is not compatible with new CIDER API
Date: Tue, 24 Jul 2018 16:54:30 +1000 [thread overview]
Message-ID: <CAC=50j_o3bD15vY7cF34VBDeDHdru5nx-16eU_GLdYoa83pkiA@mail.gmail.com> (raw)
In-Reply-To: <87efftp83f.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
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 <numbchild@gmail.com> wrote:
>
> Tim Cross <theophilusx@gmail.com> 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
[-- Attachment #2: Type: text/html, Size: 2023 bytes --]
next prev parent reply other threads:[~2018-07-24 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 11:17 ob-clojure.el is not compatible with new CIDER API stardiviner
2018-07-18 22:30 ` Tim Cross
2018-07-24 4:32 ` stardiviner
2018-07-24 6:54 ` Tim Cross [this message]
2018-07-29 11:59 ` stardiviner
2018-07-29 22:14 ` Tim Cross
2018-07-31 0:25 ` stardiviner
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=50j_o3bD15vY7cF34VBDeDHdru5nx-16eU_GLdYoa83pkiA@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=numbchild@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).