[ANN] Ultra 0.2.1 - pprint-source, and playing nicely with CIDER

2015-02-21 Thread W. David Jarvis
*Ultra: a Leiningen plugin for a superior development environment.* Release 0.2.1 comes with two changes - one feature, one (major) bugfix. *First, the feature: pprint-source* Ultra now has a function for pretty-printing source at the REPL - like `source`, but nice looking. At the moment it's s

Re: [BUG] : clojure.data/diff handles nested empty collections incorrectly

2015-02-21 Thread Andy Fingerhut
Sorry if you've already explained this and I'm missing it, but for example, suppose the current state on both sides is {:x {:y 1}}, and the 'sender' wants to change to one of these states: (a) {:x nil} (b) {:x {}} (b) {:x []} (c) {:x {:y nil}} Do you plan to support sending a different 'diff' in

Re: ANN: ClojureScript 0.0-2913, Google Closure Modules, improved nREPL support

2015-02-21 Thread Boris Kourtoukov
On Saturday, February 21, 2015 at 1:01:39 PM UTC-5, David Nolen wrote: > ClojureScript, the Clojure compiler that emits JavaScript source code. > > > README and source code: https://github.com/clojure/clojurescript > > > New release version: 0.0-2913 > > > Leiningen dependency information: >

Re: Is there a way to stop a long running expression in the REPL

2015-02-21 Thread Shawn Rasheed
Using Lein 2's REPL, Ctrl-C doesn't cancel the REPL itself. On Sat, Feb 21, 2015 at 4:45 PM, Cecil Westerhof wrote: > Sometimes I execute something that takes to long. With -C I can > cancel it, but this also cancels the REPL itself. Is there a way to > terminate the running command without term

Re: Is there a way to stop a long running expression in the REPL

2015-02-21 Thread Shawn Rasheed
If it's the clojure repl this might work: https://clojuredocs.org/clojure.repl/set-break-handler! On Sat, Feb 21, 2015 at 5:28 PM, Lucas Bradstreet wrote: > Which repl are you using? In lein repl, this does not happen to me, it > just terminates the expression. > > On 21 February 2015 at 19:45,

Re: Workaround for CLJ-1604?

2015-02-21 Thread Adam Krieg
I did build with the latest version of Clojure with the patch. I still run into the issue, although there is a twist, which could be a maven issue. I will post the details to Jira. Thanks On Friday, February 20, 2015 at 12:04:59 AM UTC-5, Andy Fingerhut wrote: > > You could build your own pat

ANN: ClojureScript 0.0-2913, Google Closure Modules, improved nREPL support

2015-02-21 Thread David Nolen
ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-2913 Leiningen dependency information: [org.clojure/clojurescript "0.0-2913"] This release comes with two very big enhancements.

Re: Default values

2015-02-21 Thread Jeremy Heiler
On 2/21/15 4:57 AM, Cecil Westerhof wrote: I want to work with default values. For this I use: [& nr] This gives the value null to nr. So far so good. But I want to propagate the value, because I want to fill the default at a higher level. ​I have: (defn test-lucky-numbers-all

Re: [ANN] Sweet Liberty: Set Your Data Free with Clojure and REST

2015-02-21 Thread Andy Chambers
On Tuesday, February 17, 2015 at 11:24:48 AM UTC-5, Bill Piel wrote: > > Blog post: > https://blog.rjmetrics.com/2015/02/15/sweet-liberty-set-your-data-free-with-clojure-and-rest/ > > > Sweet-Liberty is a library for building database-backed RESTful services > using Clojure. You can think of it

Re: Is there a way to stop a long running expression in the REPL

2015-02-21 Thread Lee Spector
In case anybody is developing tools for this kind of thing, one of the things I most miss from Common Lisp is the ability to interrupt a running expression AND see the values of locals at the point of interruption. Fantastically useful for debugging. As far as I know there's no environment that

Re: Is there a way to stop a long running expression in the REPL

2015-02-21 Thread Fluid Dynamics
It depends on what REPL/IDE you are using. In Counterclockwise there's an icon on the REPL pane's upper right with a red box near a gear, third from the left, which interrupts the currently running expression. Some other REPL environments provide similar functionality, as other people have noted

Re: Using type to change the behaviour of a function

2015-02-21 Thread Leon Grapenthin
You don't increase the performance by limiting the input value range in a pre-condition. On Thursday, February 19, 2015 at 12:52:38 PM UTC+1, Cecil Westerhof wrote: > > I have the following function: > (defn lucky-numbers > "Lucky numbers from 1 up-to upto-value. > 1 <= upto-value

Re: Is there a way to stop a long running expression in the REPL

2015-02-21 Thread Cecil Westerhof
2015-02-21 13:28 GMT+01:00 Lucas Bradstreet : > Which repl are you using? In lein repl, this does not happen to me, it > just terminates the expression. > ​I am using: rlwrap java -cp "${CP}" clojure.main --init "${CLOJURE_INIT}" --repl But maybe it is time to switch. ;-)​ > On 21 Februar

Re: Is there a way to stop a long running expression in the REPL

2015-02-21 Thread Lucas Bradstreet
Which repl are you using? In lein repl, this does not happen to me, it just terminates the expression. On 21 February 2015 at 19:45, Cecil Westerhof wrote: > Sometimes I execute something that takes to long. With -C I can cancel > it, but this also cancels the REPL itself. Is there a way to termi

Is there a way to stop a long running expression in the REPL

2015-02-21 Thread Cecil Westerhof
Sometimes I execute something that takes to long. With -C I can cancel it, but this also cancels the REPL itself. Is there a way to terminate the running command without terminating the running REPL? -- Cecil Westerhof -- You received this message because you are subscribed to the Google Groups

Re: Default values

2015-02-21 Thread Cecil Westerhof
2015-02-21 11:03 GMT+01:00 Ulises : > What's happening is that you have multiple optional arguments chained > together. Optional arguments are passed as a list (or seq?) of arguments, > so if you pass them down to another function that also takes optional > arguments they get wrapped in yet anothe

Re: Default values

2015-02-21 Thread Ulises
What's happening is that you have multiple optional arguments chained together. Optional arguments are passed as a list (or seq?) of arguments, so if you pass them down to another function that also takes optional arguments they get wrapped in yet another list. An option to stop this is to use appl

Default values

2015-02-21 Thread Cecil Westerhof
I want to work with default values. For this I use: [& nr] This gives the value null to nr. So far so good. But I want to propagate the value, because I want to fill the default at a higher level. ​I have: (defn test-lucky-numbers-all "Test all lucky number performance" [& nr

Re: No such var during runtime

2015-02-21 Thread Sven Richter
Hm, I cannot imagine how this might come into play, but in the end. I don't know. I just set the clojure version of closp to 1.7.0-alpha5, built a new jar and it still works for me. I just cannot find a way to reproduce it on my local workstation, neither on my second one where I do code from t