Re: Clojure support for Visual Studio Code

2016-09-16 Thread Michael Ball
Ok was just able to try it out briefly on OSX. - Installation went smoothly, no problems. - Explicit docs/instructions on how to start and connect to the repl would be good. I was able to get it connected but it was unclear if the repl should be started from within VS code, or from a terminal t

Re: Formatting output of pretty print using cljfmt

2016-09-16 Thread James Reeves
cljfmt doesn't currently have opinions on whether things are on one line or spread out over several lines. From cljfmt's perspective: [a b c] Is as valid as [a b c] - James On 16 September 2016 at 14:34, Amogh Talpallikar < amogh.talpalli...@gmail.com> wrote: > I have CIDER

Formatting output of pretty print using cljfmt

2016-09-16 Thread Amogh Talpallikar
I have CIDER installed with cljfmt support. I have a bunch of auto-generated clojure files with formatting done via pretty-print with badly formatted let statements. (let [a 1 b 2 c 3 d 4] (println a b c d)) Is it possible for cljfmt to format it

Re: [CfP] :clojureD 2017

2016-09-16 Thread Mars0i
On Friday, September 16, 2016 at 8:14:49 AM UTC-5, Stefan Kamphausen wrote: > > Hi, > > On Friday, September 16, 2016 at 6:16:14 AM UTC+2, Mars0i wrote: >> >> Glad that this is happening. >> You might want to add the date to the CFP and Schedule pages. I only >> found it on the Press page. >> >

Re: [CfP] :clojureD 2017

2016-09-16 Thread Stefan Kamphausen
Hi, On Friday, September 16, 2016 at 6:16:14 AM UTC+2, Mars0i wrote: > > Glad that this is happening. > You might want to add the date to the CFP and Schedule pages. I only > found it on the Press page. > Thanks for your feedback. I've added the date to the CfP page. Did you look for it on

Re: clojure.spec - suggestion on how to simplify :pre and :post conditions by using specs.

2016-09-16 Thread joakim . tengstrand
I think a natural place of the :post condition shold be after the argument brackets (and that should be possible to implement I think): (defn user-name [user :core/user] :user/name (-> user :user/name)) On Friday, September 16, 2016 at 1:34:47 PM UTC+2, joakim.t...@nova.com wrote: > > (ns sp

clojure.spec - suggestion on how to simplify :pre and :post conditions by using specs.

2016-09-16 Thread joakim . tengstrand
(ns spec-test.core (:require [clojure.spec :as s])) (s/def :user/name string?) (s/def :core/user (s/keys :req [:user/name])) ; A helper method to get better error messages. ; Also imagine that clojure.spec has a similar s/check ; function that looks similar to this one ; (used in our user-nam

Re: Clojure support for Visual Studio Code

2016-09-16 Thread Andrey Lisin
Sorry for the mess in the previous message. This code should be put into ~/.lein/profiles.clj {:user {:plugins [[cider/cider-nrepl "0.12.0-SNAPSHOT"]] :dependencies [[org.clojure/tools.nrepl "0.2.12"]]}} пятница, 16 сентября 2016 г., 17:32:54 UTC+6 пользователь Andrey Lisin написал: >

Re: Clojure support for Visual Studio Code

2016-09-16 Thread Andrey Lisin
Hi Ikuru, I've just checked and dragging and dropping works for me on Ubuntu 16.04, could you try it again? Another option is to open the extension file with "File -> Open" menu. Not sure I understand your question correctly, but to make the extension work you need to add cider-nrepl to a list

Re: clojure.spec - Using :pre conditions (or not)?

2016-09-16 Thread joakim . tengstrand
I agree with you that an IllegalArgumentException is preferable to AssertionError. The reason that I used AssertionError was that I wanted to keep the same behaviour as when using s/valid? (it throws an AssertionError). Maybe only s/assert should throw AssertionError and s/valid? should throw so