I was having the same problem as Jim and ended up just getting SLIME
working manually.
I wanted to get things set up like Vagif Verdi mentioned above so that
I can start the REPL from my own script and then connect to it from
emacs using slime-connect.
The good news is that I am using SLIME now
On Sat, Sep 12, 2009 at 4:30 PM, Phil Hagelberg wrote:
>
> Jim Menard writes:
>
>> A few comments and questions about the setup process:
>>
>> At the end of the process, the mini-buffer says, "You must specify
>> either a `swank-clojure-binary' or a `swank-clojure-classpath'. What
>> should thos
Jim Menard writes:
> A few comments and questions about the setup process:
>
> At the end of the process, the mini-buffer says, "You must specify
> either a `swank-clojure-binary' or a `swank-clojure-classpath'. What
> should those values be? I see the swank-clojure directory that has
> been ins
Jimmie Houchin writes:
> But, I do believe it is of great importance to maintain good
> contributors records to the files and its modification history
> regardless of code "ownership" but for good legal provenance.
Two things: git maintains this record automatically and much more
thoroughly
Phil,
> Jim Menard writes:
>
>> I do something similar to Brenton. I use clojure-mode, and vote for
>> keeping it as-is, making SLIME integration optional or ancillary.
>
> Could you guys give SLIME another shot via M-x clojure-install? If you
> haven't been using it because you had a hard time
On 9/11/2009 7:38 PM, Phil Hagelberg wrote:
>
> Tom Faulhaber writes:
>
>> I'm not so excited about deriving authorship data from git, though. It
>> seems like there are a lot of reasons that could be "wrong" from the
>> point of view of what we want for the documentation (how do you decide
>> wh
I use clojure-mode with slime. But i did not use clojure-install.
I also do not run clojure from within emacs. I run it via script, and
then connect to it via slime-connect.
I prefer it much more than clojure-install, because i have a control
over where my clojure and other libraries are resided
Phil Hagelberg writes:
> The solution I've settled on is the clojure-project function:
Here's what I've added to the swank-clojure codebase. It supports the
somewhat standard src/ and classes/ project layout style as well as one
based on Maven conventions.
(defun swank-clojure-project (pat
Tom Faulhaber writes:
> I'm not so excited about deriving authorship data from git, though. It
> seems like there are a lot of reasons that could be "wrong" from the
> point of view of what we want for the documentation (how do you decide
> when a checkin represents a true "co--author?", etc.).
2009/9/11 Brenton :
>
> I use clojure-mode.
>
> I have a ruby script named clj that I use to start Clojure from the
> command line and from emacs.
>
> When I set up a new Clojure project I create the following files:
>
> .cljrc.clj
> bin/
> src/
> test/
> lib/
>
> The clj script does the following
2009/9/11 Andy Kish :
>
> On Sep 10, 6:23 am, Rick Moynihan wrote:
>> As I'm sure you and many others know, this problem exists in the Java
>> community also... A few years ago I found a solution in Apache
>> Commons Launcher:
>>
>> http://commons.apache.org/launcher/
>
> Another cool launcher I
Jim Menard writes:
> I do something similar to Brenton. I use clojure-mode, and vote for
> keeping it as-is, making SLIME integration optional or ancillary.
Could you guys give SLIME another shot via M-x clojure-install? If you
haven't been using it because you had a hard time installing SLIME/
I do something similar to Brenton. I use clojure-mode, and vote for
keeping it as-is, making SLIME integration optional or ancillary.
Jim
On Fri, Sep 11, 2009 at 12:21 PM, Brenton wrote:
>
> I use clojure-mode.
>
> I have a ruby script named clj that I use to start Clojure from the
> command li
I use clojure-mode.
I have a ruby script named clj that I use to start Clojure from the
command line and from emacs.
When I set up a new Clojure project I create the following files:
.cljrc.clj
bin/
src/
test/
lib/
The clj script does the following:
1) Put the standard Clojure jars in the cla
Phil,
I didn't realize that had been implemented either, that's cool.
I'm not so excited about deriving authorship data from git, though. It
seems like there are a lot of reasons that could be "wrong" from the
point of view of what we want for the documentation (how do you decide
when a checkin
Phil thank you for your work on ESK and clojure-mode. When I started
doing more lisp stuff, I knew that I had to move from textmate to
emacs. ESK made switching a lot less daunting.
I use clojure-install (worked like a charm on debian and os x 10.6)
and clojure-update and I find them useful. They
Very much agreed on the need for a default launcher/script. This is an
annoying obstacle to adoption in my mind. Most of the "Getting Started
with Clojure" tutorials show you how to launch clojure with java and
the jar, and then provide a shell script wrapper to simplify things.
On Sep 10, 6:23 a
Tom Faulhaber writes:
> Also, one thing that I (and others) have noticed is that clojure mode
> chokes on the #^{} form metadata on namespaces. (See any of the files
> in clojure-contrib for an example.) I'm not able to reproduce the
> problem now, so if you don't already know what it is, I'll k
2009/9/9 Phil Hagelberg :
>
> The solution I've settled on is the clojure-project function:
>
> (defun clojure-project (path)
> "Setup classpaths for a clojure project and starts a new SLIME session.
> Kills existing SLIME session, if any."
> (interactive (list
>
I still use clojure-mode and it's basic LISP interaction features.
I've installed SLIME once and went through the hassle of getting it
working, but it didn't (seem) to offer much more. It also made
quitting an infinite loop difficult (C-c C-c didn't work for me in
SLIME). So eventually i just move
2009/9/10 Phil Hagelberg :
>
> Rick Moynihan writes:
>> This issue has got me thinking that the real problem appears to be
>> that there isn't a standard or default way (script) to start up and
>> run java/clojure projects... i.e. though this solves the problem when
>> running clojure programs in
Rick Moynihan writes:
> This issue has got me thinking that the real problem appears to be
> that there isn't a standard or default way (script) to start up and
> run java/clojure projects... i.e. though this solves the problem when
> running clojure programs in emacs it doesn't do so for when yo
On Sep 9, 7:44 am, "AndrewC." wrote:
> > It really does seem like there's a certain demand for it, I stumbled
> > upon several blog posts and such where people have trouble setting up
> > their Clojure projects. I definitely think that this would be a
> > worthwhile addition to clojure-mode.
I'm
Konrad Hinsen writes:
> I work with the development branch regularly updated from github. Do I
> conclude correctly that clojure-install is of no use for me?
You can let clojure-install perform the initial setup and then simply
issue a "git checkout master" from the clojure/ directory and
recomp
On Sep 9, 11:02 am, Michael Kohl wrote:
> On Wed, Sep 9, 2009 at 3:08 AM, Phil Hagelberg wrote:
> > This just resets the classpath to include target/dependency/ as well as
> > any jars in the lib/ directory of your project. I've included this in
> > the Emacs Starter Kit but haven't included i
2009/9/9 Phil Hagelberg :
>
> Rick Moynihan writes:
>
>> One problem I do have with clojure-mode/clojure is managing the
>> classpaths for clojure projects... It seems that the typical elisp
>> config only has one variable (which is then shared across all clojure
>> files) for specifying the cla
On Wed, Sep 9, 2009 at 3:08 AM, Phil Hagelberg wrote:
> This just resets the classpath to include target/dependency/ as well as
> any jars in the lib/ directory of your project. I've included this in
> the Emacs Starter Kit but haven't included it in clojure-mode yet since
> I haven't quite decid
On 8 Sep 2009, at 22:24, Phil Hagelberg wrote:
>> On the other hand, if SLIME installation is painless now, that would
>> be fine with me as well.
>
> Please give it a try and let me know if you have any problems. M-x
> clojure-install should pull in everything you need, including its own
> copy
Rick Moynihan writes:
> One problem I do have with clojure-mode/clojure is managing the
> classpaths for clojure projects... It seems that the typical elisp
> config only has one variable (which is then shared across all clojure
> files) for specifying the classpath...
>
> Personally I'd like t
Hi,
I just wanted to say thanks on the M-x clojure-install feature of
clojure-mode! I like some others on this thread used to use
clojure-mode sans SLIME, (because SLIME and the need to upgrade didn't
seem worth the installation hassle). However last week I saw
clojure-mode's M-x clojure-instal
Tom Faulhaber writes:
> Also, one thing that I (and others) have noticed is that clojure mode
> chokes on the #^{} form metadata on namespaces. (See any of the files
> in clojure-contrib for an example.) I'm not able to reproduce the
> problem now, so if you don't already know what it is, I'll k
Konrad Hinsen writes:
> On 8 Sep 2009, at 02:36, Phil Hagelberg wrote:
>> However, now that clojure-mode has the M-x clojure-install command
>> that sets up SLIME etc, I don't know if the built-in subprocess
>> features are worth keeping around any more. Personally I have never
>> used them or h
Hi Phil,
Speaking for myself, I only use SLIME & emacs 23, though I certainly
wouldn't want to force anyone to do those things.
Also, one thing that I (and others) have noticed is that clojure mode
chokes on the #^{} form metadata on namespaces. (See any of the files
in clojure-contrib for an ex
I only use SLIME for inf-Lisp jobs.
Clojure-update is a sensible complement to clojure-install, I'd
strongly vote for keeping it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group
On 8 Sep 2009, at 02:36, Phil Hagelberg wrote:
> However, now that clojure-mode has the M-x clojure-install command
> that
> sets up SLIME etc, I don't know if the built-in subprocess features
> are
> worth keeping around any more. Personally I have never used them or
> heard of anyone using
Phil Hagelberg writes:
> I'm working on cleaning up the code for clojure-mode.el, which provides
> Clojure support for Emacs.
Further things I am considering removing:
* support for Emacs 21 (which was released around 2001)
* the ability to turn off highlighting multi-line def forms
* the cloj
On Sep 7, 8:36 pm, Phil Hagelberg wrote:
> ... I don't know if the built-in subprocess features are
> worth keeping around any more. Personally I have never used them or
> heard of anyone using them; I wonder if they are just legacy baggage.
Never used them; only use SLIME. Never used clojure-i
I'm working on cleaning up the code for clojure-mode.el, which provides
Clojure support for Emacs.
It includes some functionality for interacting with subprocesses. This
is a small subset of the functionality of the functionality included in
SLIME, but it's simpler and easier to configure.
Howe
38 matches
Mail list logo
