Add the following to your ~/.lein/user.clj:
;; ~/.lein/user.clj
(if (>= (.compareTo (clojure-version) "1.3.0") 0)
(do (use 'clojure.repl)
(use 'clojure.java.javadoc)))
On Mon, Nov 14, 2011 at 10:57 PM, Yaron wrote:
> So when I start a repl from the command line things like doc and
> sour
So when I start a repl from the command line things like doc and
source work just fine.
But when I start a repl inside of aquamacs and swank clojure (1.3.3)
(installed via lein plugin) and clojure (1.3.0) via m-x clojure-jack-
in those function/macros don't work at all. For example, if I try (doc
Tim,
I've been wanting this for some time. Obviously the java interop stuff poses
challenges, but the clojure data types, protocols, immutable objects, clojure
syntax, etc... would make for a nice dialect of lisp to be used alongside other
CL code. (I guess I'm in the small minority of folks t
Oh, I was thinking of defvar from Common Lisp. I didn't realize contrib's
version was different; curious.
-Phil
On Nov 14, 2011 8:37 PM, "Alan Malloy" wrote:
> On Nov 14, 7:44 pm, Phil Hagelberg wrote:
> > On Mon, Nov 14, 2011 at 4:26 PM, Alan Malloy wrote:
> > > (def name doc init)
> >
> > Ac
On Nov 14, 7:44 pm, Phil Hagelberg wrote:
> On Mon, Nov 14, 2011 at 4:26 PM, Alan Malloy wrote:
> > (def name doc init)
>
> Actually defvar is more like defonce.
Huh? I don't see any defonce semantics at
https://github.com/clojure/clojure-contrib/blob/master/modules/def/src/main/clojure/clojure/
I discovered tree-seq the other day and it seems like a nice little
function for elegantly dealing with a tree of values. In standard OO,
I would use autocompletion to find the right variable as I loop over
an OO data structure, but tree-seq seems very flexible and generic.
That's all I wanted to
On Mon, Nov 14, 2011 at 4:26 PM, Alan Malloy wrote:
> (def name doc init)
Actually defvar is more like defonce.
-Phil
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from
Structmaps can be defined either named, thru the defstruct macro, or
anonymously, thru the create-struct function call. Record types must
be named and defined thru a call to defrecord.
This seems to contradict one of the Clojure library coding standards
(http://dev.clojure.org/display/design/Libr
I've updated Where Did Clojure Contrib Go to indicate this. Happy to
take other suggestions for updates!
On Mon, Nov 14, 2011 at 6:36 PM, Brad wrote:
> Thanks. I couldn't find this mentioned anywhere so I added a comment
> on clojuredocs
>
> http://clojuredocs.org/clojure_contrib/clojure.contrib.
Thanks. I couldn't find this mentioned anywhere so I added a comment
on clojuredocs
http://clojuredocs.org/clojure_contrib/clojure.contrib.def/defvar
On Nov 14, 7:26 pm, Alan Malloy wrote:
> (def name doc init)
>
> On Nov 14, 4:03 pm, Brad wrote:
>
>
>
>
>
>
>
> > I'm working on moving to Clo
On Mon, 2011-11-14 at 16:26 -0800, Phil Hagelberg wrote:
> On Mon, Nov 14, 2011 at 4:18 PM, daly wrote:
> > It seems to me that a Clojure in Common Lisp might be the
> > easiest non-JVM port. It would be a DSL within Common Lisp.
> > A CL implementation would even allow rewriting the normal
> > C
Hello folks.
You may have heard some rumours and/or tweetage about Cake and
Leiningen. During the Conj I met with Justin Balthrop and some of the
other Cake developers. They were interested in joining forces to
develop a single unified build tool for Clojure. We talked it through
and I think Leini
On Mon, Nov 14, 2011 at 4:18 PM, daly wrote:
> It seems to me that a Clojure in Common Lisp might be the
> easiest non-JVM port. It would be a DSL within Common Lisp.
> A CL implementation would even allow rewriting the normal
> COND syntax. Is there an obvious reason why this would be
> a bad ide
(def name doc init)
On Nov 14, 4:03 pm, Brad wrote:
> I'm working on moving to Clojure 1.3
>
> Some code is using defvar which use to be in clojure.contrib.def
>
> http://dev.clojure.org/display/design/Where+Did+Clojure.Contrib+Go
> mentions that contrib.def partially migrated to clojure.core.inc
It seems to me that a Clojure in Common Lisp might be the
easiest non-JVM port. It would be a DSL within Common Lisp.
A CL implementation would even allow rewriting the normal
COND syntax. Is there an obvious reason why this would be
a bad idea?
Heck, it might even be possible to make the port lit
I'm working on moving to Clojure 1.3
Some code is using defvar which use to be in clojure.contrib.def
http://dev.clojure.org/display/design/Where+Did+Clojure.Contrib+Go
mentions that contrib.def partially migrated to clojure.core.incubator
but this new library doesn't appear to have it.
Is ther
> You still need to load the properties and tell the logger to use them.
> Assuming it is using log4j, something like the following should do
> that (completely untested though):
>
> ...
> (:require [clojure.java.io :as io])
> ...
> (with-open [s (io/input-stream (io/resource "logging.properties"
> I put a logging.properties file in the resources directory of the project
> but it does not seem to pick it up. Do I have to do something else to
> override the default logging from the java library I am using?
You still need to load the properties and tell the logger to use them.
Assuming it i
I put a logging.properties file in the resources directory of the project
but it does not seem to pick it up. Do I have to do something else to
override the default logging from the java library I am using?
On , Phil Hagelberg wrote:
On Mon, Nov 14, 2011 at 9:22 AM, joegallo joega...@gmail.
On Mon, Nov 14, 2011 at 9:22 AM, joegallo wrote:
> You could drop it into the root of src, or you can add a :resources-path
> "etc" in your project.clj and then put it in the root of that. Some purists
> would probably argue that the latter is better, but the former should work
> just fine, too.
You could drop it into the root of src, or you can add a :resources-path
"etc" in your project.clj and then put it in the root of that. Some
purists would probably argue that the latter is better, but the former
should work just fine, too.
--
You received this message because you are subscrib
Here's a patch:
http://code.google.com/p/clojure-jsr223/downloads/list
Feel free to file bugs here:
http://code.google.com/p/clojure-jsr223/issues/list
On Nov 13, 9:52 am, Francesco wrote:
> I was trying to write a simple script attribute definition for
> shibboleth as
> in:https://wiki.shibbol
I'm interfacing with a java library. I'm getting logging info messages.
Where do I put the logging.properties file in a lein project?
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note
I'm interfacing with a java library. I'm getting logging info messages.
Where do I put the logging.properties file in a lein project?
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note
The compile call is a no-op and makes no difference since the engine
evaluates the script. That looks like a bug in getAttribute(). I use
put and get from the engine directly and may have overlooked something
in the attr calls. I'll upload a fix in google code asap.
On Nov 13, 9:52 am, Francesco
25 matches
Mail list logo
