emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Soapy Smith <soapy-smith@comcast.net>
Cc: org mode <emacs-orgmode@gnu.org>, Oleh <ohwoeowho@gmail.com>,
	Eric Schulte <schulte.eric@gmail.com>
Subject: Re: update to ob-clojure.el
Date: Thu, 17 Apr 2014 20:51:37 +0200	[thread overview]
Message-ID: <87vbu7x006.fsf@bzg.ath.cx> (raw)
In-Reply-To: <1397402434.2038.7.camel@raven-CM5571> (Soapy Smith's message of "Sun, 13 Apr 2014 11:20:34 -0400")

Hi Greg and Oleh,

Soapy Smith <soapy-smith@comcast.net> writes:

> I'm not sure about removing nrepl and slime, as there may be some still
> using them, especially nrepl.  As long as it is not getting in the way,
> perhaps at this time it would be better to leave them in?

Agreed.

> I'm not sure
> the open-source and/or emacs-org philosophy on this kind of thing.

"If it ain't broken, don't fix it."

> Prior to updating the documentation for Clojure code blocks earlier this
> year, which was several years old, I did a lot of searching around and
> came to the conclusion that the slime and swank-clojure functionality
> was no longer being developed, and the community had moved on to nrepl.
> CIDER evolved from nrepl, and is the current direction.
>
> https://github.com/clojure-emacs/cider
>
> The revised documentation is very "CIDER-centric":
>
> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-clojure.html

Yes, we shall put all efforts into supporting CIDER, and then ping the
Clojure community to know whether slime and nrepl still need to be
supported.  But for Org 8.3, let's continue to have those.

-- 
 Bastien

      parent reply	other threads:[~2014-04-17 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10  8:36 update to ob-clojure.el Oleh
2014-04-10  9:44 ` Nicolas Goaziou
2014-04-10 10:53   ` Oleh
2014-04-11 10:04     ` Bastien
2014-04-13 15:20 ` Soapy Smith
2014-04-14 10:11   ` Oleh
2014-04-17 18:51   ` Bastien [this message]

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=87vbu7x006.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=ohwoeowho@gmail.com \
    --cc=schulte.eric@gmail.com \
    --cc=soapy-smith@comcast.net \
    /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).