From: Per Bothner <per@bothner.com>
To: "Rafik Naccache (TNTeam Rocks!)" <rafik@tnteam.rocks>,
kawa@sourceware.org
Subject: Re: RE : Re: What is the Development Environment of Choice for Kawa?
Date: Thu, 18 Feb 2016 21:18:00 -0000 [thread overview]
Message-ID: <56C6351E.90107@bothner.com> (raw)
In-Reply-To: <3go6arm3yvsi6iuungnfyd1o.1455824305674@email.android.com>
On 02/18/2016 11:38 AM, Rafik Naccache (TNTeam Rocks!) wrote:
> Actually I managed to use swank/sLime with Kawa. But half of its functionality is broken.
I'm afraid Swank/Slime with Kawa isn't actively maintained.
Helmut Eller wrote/maintained it, but he is no longer involved.
I don't know the details - it maybe that the Swank model isn't
a great match for Kawa's more static binding mode - or for the JVM.
OTOH if you have experience with and were productive with Swank/Clojure,
perhaps we can get Swank/Kawa working, possibly by studying how Clojure does things.
> I am an emacs guy so this probably helps me, especially as I use smartparens (a new paredit) ans rainbow delimiters.
>
> Maybe I shall write a Kawa.el mode on emacs Like cider fir clojure, in which case I 'll need some hints on how completion works, etc...
>
> @ Per, When do you plan to release the code hot loading fixes in SVN?
I don't have anything usable at this point, and I'm back-logged on other
projects (DomTerm; Kawa arrays; Kawa new invocation model with patterns; more)
that I don't know when I'll be able to spend time on it. It's moderately
high priority, but so is finishing up various half-finished projects!
Until then, you can try the --no-inline flag, and be prepared to re-load
everything after changes. One of the big advantages of Kawa that its
fast compiler and loading makes re-starting ok.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next parent reply other threads:[~2016-02-18 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3go6arm3yvsi6iuungnfyd1o.1455824305674@email.android.com>
2016-02-18 21:18 ` Per Bothner [this message]
2016-02-18 21:22 ` mikel evins
2016-02-18 22:24 ` RE : " Rafik
2016-02-18 22:38 ` Per Bothner
2016-02-19 0:09 ` Alex Shinn
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=56C6351E.90107@bothner.com \
--to=per@bothner.com \
--cc=kawa@sourceware.org \
--cc=rafik@tnteam.rocks \
/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.
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).