Re: cider-repl show java and clojure version nil

[Bozhidar Batsov]

You're using a very old version of nREPL, which is likely coming from an
older version of lein. Try using the latest the latest leiningen.

On 3 February 2015 at 16:29, SK Kim  wrote:

> Hello all,
>
> This is what cider-repl shows right after cider-jack-in.
>
> ; CIDER 0.9.0alpha (package: 20150131.203) (Java nil, Clojure nil, nREPL
> 0.2.3)
> user>
>
> It shows java and clojure version nil.
>
> *clojure-version* value is as below:
> user> *clojure-version*
> {:major 1, :minor 6, :incremental 0, :qualifier nil}
>
>
> Looks like everything works fine but it is annoying to watch it everytime.
> If anybody knows the reason, pls help me.
> Thanks.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ANN: vim-cljfmt: a vim plugin for cljfmt, the Clojure formatting tool

[Bozhidar Batsov]

Nice!

I think it'd be a good idea to wrap cljfmt in a nREPL middleware that we
can use from both CIDER and fireplace (and possibly other editors). I might
look into adding this to cider-nrepl.

On 4 February 2015 at 19:07, W. David Jarvis  wrote:

> Today I'm open sourcing vim-cljfmt (
> https://github.com/venantius/vim-cljfmt). As the name implies, it's a vim
> plugin for weavejester's cljfmt, intended to fit into the vim developer's
> workflow much as gofmt does, with a BufWritePre hook to format your code on
> write. It leverages Fireplace.vim's quasi-REPL to do the formatting, so it
> doesn't cause Vim to hang while waiting for Lein to run, either (the
> initial `require` of the cljfmt namespace into the REPL will take a sec, of
> course, but you'll only have to do it once).
>
> Feedback, bug reports, etc. very welcome.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Dunaj project, an alternative core API for Clojure

[Bozhidar Batsov]

You might want to add some commenting capabilities to those articles.
They'll be more valuable in the context of discussions IMO.

On 6 March 2015 at 18:49, Jozef Wagner  wrote:

> Experiment #1
>
> *Deconstructing Core API*
>
> While Clojure provides its functionalities in multiple namespaces (e.g.
> clojure.string, clojure.zip), the majority of it is defined in a single
> namespace called clojure.core. The first Dunaj experiment explores the idea
> of having multiple small namespaces where functions, macros and other
> public vars are grouped by their purpose. It investigates whether such
> separation is possible at all and whether it can be practical and useful.
>
> The goals of the first Dunaj experiment are as follows:
>
> - Devise a new user centric core API comprising multiple namespaces,
> leaving bootstrapping and low level vars in the clojure.core.
>
> - Define a concept of API presets that control which functions, macros and
> vars gets referred by default.
>
> - Let user choose which API preset he/she wants to use in his/hers
> namespace, using classic clojure.core as a default.
>
> The upside of this approach is that backwards compatibility is maintained
> and users can freely intermix multiple APIs in their projects.
> Functionalities can be more logically separated by their purpose. List of
> automatically referred vars are no longer driven by the namespace in which
> they were defined, but this list is handled by separate API presets that
> can be extended and customized.
>
> You can read more about this experiment at http://www.dunaj.org
>
> -- Jozef
>
>
> On Thu, Mar 5, 2015 at 10:33 PM, Jozef Wagner 
> wrote:
>
>> I'm happy to announce a project called Dunaj [1], which provides an
>> alternative core API for Clojure. Its main aim is to experimentally test
>> major additions to the language.
>>
>> Dunaj /ˈdunaɪ/ is a set of core language experiments aimed to improve
>> Clojure language and its core API. It deals with language features that
>> require changes across different parts of Clojure and which cannot be
>> evaluated in isolation. Dunaj aims to bring Clojure even more towards
>> simplicity, consistency and performance.
>> It is intended to be used by regular Clojure developers, either for
>> application or library development.
>>
>> Dunaj was created to test 10 experiments that bring significant changes
>> to the Clojure language. As there is a substantial number of additions and
>> changes, I want to try a bit unconventional approach here. Before I'll
>> release the actual library, I will introduce Dunaj's experiments in a
>> series of individual posts. Every part states the motivation behind the
>> experiment, introduces changes and additions to the language and
>> demonstrates its intended use. If you do not want to miss any of this, you
>> may want to register for a mailing list at [1] or follow @dunajproject at
>> Twitter.
>>
>> -- Jozef Wagner
>>
>> [1] http://www.dunaj.org/
>>
>>
>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Debugging in CIDER

[Bozhidar Batsov]

Hey everyone,

Just wanted to let you know that the most requested feature for CIDER (a
debugger, in case you're wondering) has just landed in the master branch (
https://github.com/clojure-emacs/cider/pull/1019#issuecomment-87240470).

The new CIDER debugger is inspired by edebug (Emacs's own debugger) and
based on https://github.com/razum2um/clj-debugger

It's not super fancy and there's clearly room for improvement in both
clj-debugger and CIDER itself, but it's a pretty good first step. Please,
take the new debugger out for a spin and let us know what do you think
about it. You might also report any problems you've encountered. :-)

If all is well, CIDER 0.9 will probably be released in a week or so.

P.S. Thanks, Artur (https://github.com/Malabarba), for all the hard work on
the debugger! You've once again showed the power of the OSS! There's
nothing we can't build together!

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: clojure, not the go to for data science

[Bozhidar Batsov]

And CIDER isn't, right? I find this pretty insulting...

On 29 March 2015 at 13:47, Colin Yates  wrote:

> Cursive Clojure, LightTable and CounterClockwise are all good Clojure IDEs.
>
> On 29 March 2015 at 09:54, Sayth Renshaw  wrote:
> > Hi
> >
> > I last learned clojure in 1.2. Just curious why Clojure hasn't developed
> as a go to for data science?
> >
> > It never seems to get a mention R,Python and now Julia get the
> attention. By design it would appear that Clojure would be a good fit. Is
> it a lack of libraries, ease of install, no good default environment  (R
> Rstudio, IPython ) where as you would need to use emacs with clojure, or is
> there just a better default use of Clojure?
> >
> > Sayth
> >
> > --
> > 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 new members are moderated - please be patient with
> your first post.
> > To unsubscribe from this group, send email to
> > clojure+unsubscr...@googlegroups.com
> > For more options, visit this group at
> > http://groups.google.com/group/clojure?hl=en
> > ---
> > You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to clojure+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: clojure, not the go to for data science

[Bozhidar Batsov]

Just picking on the wording, that's all. Anti-Emacs stuff really gets to
me. Forget I ever said anything.

On 29 March 2015 at 17:17, Colin Yates  wrote:

> I assumed his reference to emacs covered CIDER - don't be so sensitive :).
>
> On 29 March 2015 at 15:14, Bozhidar Batsov  wrote:
> > And CIDER isn't, right? I find this pretty insulting...
> >
> >
> > On 29 March 2015 at 13:47, Colin Yates  wrote:
> >>
> >> Cursive Clojure, LightTable and CounterClockwise are all good Clojure
> >> IDEs.
> >>
> >> On 29 March 2015 at 09:54, Sayth Renshaw 
> wrote:
> >> > Hi
> >> >
> >> > I last learned clojure in 1.2. Just curious why Clojure hasn't
> developed
> >> > as a go to for data science?
> >> >
> >> > It never seems to get a mention R,Python and now Julia get the
> >> > attention. By design it would appear that Clojure would be a good
> fit. Is it
> >> > a lack of libraries, ease of install, no good default environment  (R
> >> > Rstudio, IPython ) where as you would need to use emacs with clojure,
> or is
> >> > there just a better default use of Clojure?
> >> >
> >> > Sayth
> >> >
> >> > --
> >> > 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 new members are moderated - please be patient
> with
> >> > your first post.
> >> > To unsubscribe from this group, send email to
> >> > clojure+unsubscr...@googlegroups.com
> >> > For more options, visit this group at
> >> > http://groups.google.com/group/clojure?hl=en
> >> > ---
> >> > You received this message because you are subscribed to the Google
> >> > Groups "Clojure" group.
> >> > To unsubscribe from this group and stop receiving emails from it, send
> >> > an email to clojure+unsubscr...@googlegroups.com.
> >> > For more options, visit https://groups.google.com/d/optout.
> >>
> >> --
> >> 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 new members are moderated - please be patient with
> >> your first post.
> >> To unsubscribe from this group, send email to
> >> clojure+unsubscr...@googlegroups.com
> >> For more options, visit this group at
> >> http://groups.google.com/group/clojure?hl=en
> >> ---
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Clojure" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to clojure+unsubscr...@googlegroups.com.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> >
> > --
> > 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 new members are moderated - please be patient with
> your
> > first post.
> > To unsubscribe from this group, send email to
> > clojure+unsubscr...@googlegroups.com
> > For more options, visit this group at
> > http://groups.google.com/group/clojure?hl=en
> > ---
> > You received this message because you are subscribed to the Google Groups
> > "Clojure" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to clojure+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How do I upgrade nREPL?

[Bozhidar Batsov]

Yeah, other have noticed this as well
https://github.com/clojure-emacs/cider/issues/961

Not sure if this is a Lein bug or a feature.

On 30 March 2015 at 10:09, Shannon Severance  wrote:

> Through some additional experimentation, I have found when I start
> Leiningen repl within a Leiningen project, the nrepl dependency from
> ~/.lien/profiles.clj is being used. nREPL 0.2.10 is started. This is true
> if I start via `lein repl` or `cider-jack-in`.
>
> The problem exists when starting free of a project.
>
> -- Shannon
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: State of the Art in Clojure Debugging

[Bozhidar Batsov]

This is a newish REPL debugger that's editor agnostic -
https://github.com/razum2um/clj-debugger (and accidentally it's powering
CIDER's own debugger).

I'm pretty sure Cursive has the most sophisticated debugger right now, so
the question is whether you dislike Intellij IDEA as much as Emacs. :-)



On 30 March 2015 at 15:20, Matthew West  wrote:

> What is the current preferred strategy for debugging Clojure code? I'd
> prefer a solution that doesn't involve Emacs, as I already know vim pretty
> well and don't really want to switch. What are my options that are still
> actively maintained?
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: anybody here who use emacs to edit closure? is emacs lisp a good starting point to learn closure?

[Bozhidar Batsov]

You can definitely start using Emacs without having to learn Emacs Lisp.
Unless you're planning to write some custom extensions or customize your
setup wildly you can go a very long way with just cursory knowledge of
Emacs Lisp. At any rate - knowing any Lisp dialect makes it relatively easy
to pick up other dialects. I had learned Common Lisp back in the day and
this made it pretty easy for me to pick up Emacs Lisp when I had to dive
deeper into it.

I'm kind of biased, but I believe that the Emacs tooling for Clojure is
pretty nice. :-) If you're in to IDEs, however, guess you should check out
Cursive or CCC instead.

On 4 April 2015 at 05:46, Juvenn Woo  wrote:

> Agree with Andy. As a starter, it is better and faster to learn Clojure
> alone. After you grasped one, the other lisps will be easy to follow.
>
> Emacs has been the de facto goto choice for most here, it is highly
> recommended to invest into it. Other than that, there're vim fireplace, as
> well as IDE plugin Cursive that might be your liking.
>
> PS: I use vim + fireplace :)
>
> —
> Sent from Mailbox 
>
>
> On Sat, Apr 4, 2015 at 10:02 AM, Andy Fingerhut 
> wrote:
>
>> If your goal is to learn Clojure, I would recommend not learning Emacs
>> Lisp at the same time, just to avoid confusion that may arise in your mind
>> due to the differences between the two.
>>
>> You can use Emacs without learning Emacs Lisp with no problem.  I've used
>> Emacs for 20 years, and only know a little tiny bit of Emacs Lisp.
>>
>> Andy
>>
>> On Fri, Apr 3, 2015 at 6:54 PM,  wrote:
>>
>>> i am about to use emas and start to learn emacs lisp, would the study of
>>> emacs lisp help to learn clojure, both of them are lisp dialect, so would
>>> it take a long time to swich from emacs lisp to clojure?
>>> i just want to learn clojure, but i wanna to start from emacs and emacs
>>> lisp, is that an effective way to master lisp and the great editor emacs?
>>> or it's better to start from clojure and some other ide directly?
>>> need some suggestions and advices:)
>>>
>>> --
>>> 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 new members are moderated - please be patient with
>>> your first post.
>>> To unsubscribe from this group, send email to
>>> clojure+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/clojure?hl=en
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to clojure+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> 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 new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: anybody here who use emacs to edit closure? is emacs lisp a good starting point to learn closure?

[Bozhidar Batsov]

Ops, I meant to say CCW, not CCC. :-)

On 4 April 2015 at 10:43, Laurent PETIT  wrote:

> Please also note that Counterclockwise, the Eclipse plugin for Clojure,
> also comes with all all-inclusive zip archive which makes you as easy to
> start creating a new project as "Download / Unzip / Start":
>
> http://doc.ccw-ide.org/documentation.html#install-as-standalone-product
>
> 2015-04-04 3:54 GMT+02:00 :
>
>> i am about to use emas and start to learn emacs lisp, would the study of
>> emacs lisp help to learn clojure, both of them are lisp dialect, so would
>> it take a long time to swich from emacs lisp to clojure?
>> i just want to learn clojure, but i wanna to start from emacs and emacs
>> lisp, is that an effective way to master lisp and the great editor emacs?
>> or it's better to start from clojure and some other ide directly?
>> need some suggestions and advices:)
>>
>> --
>> 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 new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Laurent Petit
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Lein repl and Cider repl

[Bozhidar Batsov]

Maybe reply interns `clojure.repl/doc` in every namespace. I can tell you
for a fact that in CIDER the `clojure.repl` functions are interned only in
the "user" namespace. We can always change this, but it doesn't make a lot
of sense. CIDER users normally never use functions like "doc" as they have
much more powerful options at their disposal (e.g. `C-c C-d d` (cider-doc)
or the `C-c C-d g`).

On 5 April 2015 at 11:41, andrea crotti  wrote:

> Hi guys, one question about the Repl and Cider.
>
> When I start the Repl with "lein repl", I am in the namespace "x.y",
> and if I do "(doc swap!)" I see the documentation showing up.
>
> If instead I start the repl with Cider, it looks like I'm in the same
> namespace, however "(doc swap!)" doesn't work, but if I do
> "(clojure.repl/doc swap!)" actually works.
>
> So I wonder what's the difference, how does running "lein repl" differ
> from using the cider repl?
>
> Is it possible to have the same behaviour in both?
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Lein repl and Cider repl

[Bozhidar Batsov]

"find-doc" -> "cider-apropos"

Go through the CIDER readme - it's full of useful tips.

On 5 April 2015 at 12:45, andrea crotti  wrote:

> Ah thanks awesome, yes that's true I only have to get used to the Cider.
> The only thing is not also in Cider then would be "find-doc"?
>
> And in general, what would be the best way to add some extra
> customization to how the Cider repl works?
>
> 2015-04-05 9:46 GMT+01:00 Bozhidar Batsov :
> > Maybe reply interns `clojure.repl/doc` in every namespace. I can tell you
> > for a fact that in CIDER the `clojure.repl` functions are interned only
> in
> > the "user" namespace. We can always change this, but it doesn't make a
> lot
> > of sense. CIDER users normally never use functions like "doc" as they
> have
> > much more powerful options at their disposal (e.g. `C-c C-d d`
> (cider-doc)
> > or the `C-c C-d g`).
> >
> > On 5 April 2015 at 11:41, andrea crotti 
> wrote:
> >>
> >> Hi guys, one question about the Repl and Cider.
> >>
> >> When I start the Repl with "lein repl", I am in the namespace "x.y",
> >> and if I do "(doc swap!)" I see the documentation showing up.
> >>
> >> If instead I start the repl with Cider, it looks like I'm in the same
> >> namespace, however "(doc swap!)" doesn't work, but if I do
> >> "(clojure.repl/doc swap!)" actually works.
> >>
> >> So I wonder what's the difference, how does running "lein repl" differ
> >> from using the cider repl?
> >>
> >> Is it possible to have the same behaviour in both?
> >>
> >> --
> >> 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 new members are moderated - please be patient with
> >> your first post.
> >> To unsubscribe from this group, send email to
> >> clojure+unsubscr...@googlegroups.com
> >> For more options, visit this group at
> >> http://groups.google.com/group/clojure?hl=en
> >> ---
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Clojure" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to clojure+unsubscr...@googlegroups.com.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> >
> > --
> > 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 new members are moderated - please be patient with
> your
> > first post.
> > To unsubscribe from this group, send email to
> > clojure+unsubscr...@googlegroups.com
> > For more options, visit this group at
> > http://groups.google.com/group/clojure?hl=en
> > ---
> > You received this message because you are subscribed to the Google Groups
> > "Clojure" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to clojure+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Clojure Applied: From Practice to Practitioner

[Bozhidar Batsov]

IMO "Clojure Programming" is the best intro book (although it's a bit
outdated). "Clojure for the Brave and the True" is great as well, but it's
not yet completely finished (ETA June).

On 9 April 2015 at 18:57, Derek Koziol  wrote:

> What do you recommend as "fine introductory books" to get myself at the
> level needed for this book? I have very little experience with functional
> programming and Clojure.
>
>
> On Wednesday, April 8, 2015 at 9:27:58 AM UTC-4, Alex Miller wrote:
>>
>> Hey all,
>>
>> I'm very happy to announce that Clojure Applied is now available in beta:
>>
>> https://pragprog.com/book/vmclojeco/clojure-applied
>>
>> I've been working on this with Ben Vandgrift for a long time, hoping to
>> fill the underserved niche of *intermediate* Clojure material. Our goal
>> is to step in after you've read any of the fine introductory books and
>> provide the next level of guidance needed to successfully apply Clojure to
>> real problems.
>>
>> The chapters are:
>>
>> 1. Model Your Domain - an overview of modeling domain entities, modeling
>> relationships, validating them, and creating domain operations.
>> 2. Collect And Organize Your Data - choosing the right collection,
>> updating collections, accessing collections, and building custom
>> collections.
>> 3. Processing Sequential Data - using sequence functions and transducers
>> to transform your data.
>> 4. State, Identity, and Change - modeling change and state with Clojure's
>> state constructs.
>> 5. Use Your Cores - waiting in the background, queues and workers,
>> parallelism with reducers, and thinking in processes with core.async.
>> 6. Creating Components - organizing your code with namespaces, designing
>> component APIs, connecting components with core.async channels, and
>> implementing components with state.
>> 7. Compose Your Application - assembling components, configuration, and
>> entry points.
>> 8. Testing Clojure - example- and property-based testing with
>> clojure.test, expectations, and test.check.
>> 9. Playing With Others - details TBD
>> 10. Getting Out The Door - publishing your code and deploying your
>> application.
>>
>> Chapters 1-6 and 10 are available now in beta form. We expect to release
>> a new chapter every 2-3 weeks until completion. The printed book should be
>> available this fall.
>>
>> Alex
>>
>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ClojureScript] Re: ANN: ClojureScript 0.0-3196, Conditional Reading, REPLs, and Code Motion

[Bozhidar Batsov]

Btw, CIDER 0.9-snapshot was just updated and now works with the latest
ClojureScript release.

On 11 April 2015 at 18:15, David Nolen  wrote:

> Yep, the clojure.main option is the one you want.
>
> David
>
> On Sat, Apr 11, 2015 at 10:45 AM, Georgi Danov 
> wrote:
>
>> I did read it very carefully several times, but kept trying to use it via
>> remote connection (headbang).
>>
>> I got it running using the config "use clojure.main in normal JVM
>> process", is this how it's supposed to be?
>>
>>
>> On Saturday, April 11, 2015 at 4:06:47 PM UTC+2, David Nolen wrote:
>> > I was able to connect IntelliJ to a REPL because Cursive can now
>> connect to a ClojureScript REPL started in the usual way. There is no
>> special setup, make sure you've taken the time to read the new
>> ClojureScript Quick Start.
>> >
>> >
>> > HTH,
>> > David
>> >
>> >
>> > On Sat, Apr 11, 2015 at 5:06 AM, Georgi Danov 
>> wrote:
>> >
>> > Hi,
>> >  I keep having troubles running repl with piggieback and once again I
>> see in the changelog this was improved. I also saw the screenshot in your
>> last tweet which clearly shows intellij can connect.
>> >
>> >  Can you please share your project set-up? Some sort of sample project
>> that has that up & running would be of great value.
>> >
>> >  Even when I follow the tutorials I end up in weird exceptions, last
>> one being
>> >
>> > No implementation of method: :-evaluate of protocol:
>> #'cljs.repl/IJavaScriptEnv found for class: clojure.lang.PersistentArrayMap
>> > at clojure.core$_cache_protocol_fn.invoke(core_deftype.clj:554)
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> >
>> > Note that posts from new members are moderated - please be patient with
>> your first post.
>> >
>> > ---
>> >
>> > You received this message because you are subscribed to the Google
>> Groups "ClojureScript" group.
>> >
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an email to clojurescrip...@googlegroups.com.
>> >
>> > To post to this group, send email to clojur...@googlegroups.com.
>> >
>> > Visit this group at http://groups.google.com/group/clojurescript.
>>
>> --
>> Note that posts from new members are moderated - please be patient with
>> your first post.
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ClojureScript" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojurescript+unsubscr...@googlegroups.com.
>> To post to this group, send email to clojurescr...@googlegroups.com.
>> Visit this group at http://groups.google.com/group/clojurescript.
>>
>
>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] edn.el

[Bozhidar Batsov]

Using EDN instead of bencode with nREPL & CIDER comes to mind. Leveraging
the socketed REPL in Clojure 1.7 from Emacs would be another idea.

On 14 April 2015 at 00:25, Blake Miller  wrote:

> Cool! May I ask what your motivation was for this?
>
>
> On Saturday, April 11, 2015 at 3:09:28 AM UTC-7, Lars Andersen wrote:
>>
>>  https://github.com/expez/edn.el
>>
>> is a library for reading an writing edn from emacs lisp.
>>
>>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN, GSoC] A Common Clojure Source Metadata Model

[Bozhidar Batsov]

I think the real problem is the lack of conventions for adding metadata to
docstrings. I sorely miss `some-func/var' and SOME-PARAM from Emacs Lisp.
It's always
clear where you refer to other functions/variables and to parameters. This
makes it way easier to read (and parse) a docstring.

On 6 May 2015 at 14:17, Phillip Lord  wrote:

>  writes:
> > The goal of this project is to develop a comprehensive and extensible
> > model for describing Clojure sources from an API perspective. I will
> > also write a program that analyses Clojure sources according to this
> > model and outputs data documenting their usage. This could be compared
> > to Javadoc, but emitting data to be consumed by other tools instead of
> > HTML. In order to foster adoption, I will provide extensive
> > documentation, including examples of such consumer tools, and
> > emphasize active communication with the community. ☙
>
> I would like to see a mechanism for structure in the clojure doc
> strings. So, consider the second definition in core.clj.
>
>
> (def
>  ^{:arglists '([x seq])
> :doc "Returns a new seq where x is the first element and seq is
> the rest."
>:added "1.0"
>:static true}
>
>  cons (fn* ^:static cons [x seq] (. clojure.lang.RT (cons x seq
>
> Analysing this further:
>
> Returns a new seq where x is the first element and seq is the rest.
>
> We have two uses of 'seq', where one refers to the general concept (or
> to the interface ISeq), and the other refers to the parameter defined in
> :arglists. We have 'x' which refers to an :arglists parameter also. And
> we have 'first', 'rest' and 'seq' none of which refer to the function
> names in the same namespace as cons. Although they might do if the doc
> string were reworded:
>
> Returns a new ISeq, s, where (first s) returns x and (rest s)
> returns seq.
>
>
> Not sure whether this is in scope or not, but it is about usage of
> metadata.
>
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ClojureCLR and nrepl ?

[Bozhidar Batsov]

Btw, even if there were working nREPL for CLR you'll still have issues with
fireplace as both of its modes (using embedded tooling code & using nREPL
middleware) rely on JVM libs. Same goes for CIDER, of course. Outside of
basic evaluation pretty much nothing will work.

On 7 May 2015 at 05:33, dmiller  wrote:

> Not completely functional and not thoroughly tested.
> Several tests still fail -- the most important one being interrupting an
> eval.  (I know what the fix is, but haven't had the time.)
>
>
> On Wednesday, May 6, 2015 at 3:58:34 PM UTC-5, Alex Miller wrote:
>>
>> https://github.com/clojure/clr.tools.nrepl
>>
>> On Wednesday, May 6, 2015 at 3:39:18 PM UTC-5, rogergl wrote:
>>>
>>> Does ClojureCLR provide an nrepl implementation that would allow
>>> vim.fireplace to connect to his session ?
>>>
>>> Regards
>>>   Roger
>>>
>>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

[Bozhidar Batsov]

I'll just say one more time that the team should really consider doing
bug-fix releases in the future. This problem sounds serious enough to be
handled as quickly as possible. Clojure 1.6 was released over one year ago,
so I'm guessing 1.8 is more than a year away from now. Waiting for major
releases for a bug fix in not exactly the greatest user experience.

On 9 May 2015 at 05:18, Alexander Hudek  wrote:

> I'd like to chime in here in support of this, our company has been running
> a modified clojure build because of this for over a year now.
>
> Alex
>
>
> On Friday, May 8, 2015 at 2:12:50 PM UTC-4, Martin Raison wrote:
>>
>> Hi all,
>>
>> This issue has been around for a while without much activity, although a
>> very simple fix is already there:
>> http://dev.clojure.org/jira/browse/CLJ-703
>>
>> We have a pretty big Clojure project that we compile on machines with
>> slow hard-drives, on CentOS 6. We noticed that compilation had become
>> extremely slow, however CPU usage was always below 10%.
>>
>> Simply removing the line "cfs.getFD().sync();" inside 
>> "src/jvm/clojure/lang/Compiler.java"
>> dramatically improved the compilation time (Something like 10x, although at
>> this level of increase, measurement almost doesn't make sense anymore :)).
>>
>> We've been using the suggested fix (remove-sync-only.patch) for a few
>> weeks and haven't observed any issues.
>>
>> It seems we should really figure out whether this line is actually
>> necessary, or if it was added there "just in case". Even if some situations
>> require it, the speed bump is so huge that we might want some special-case
>> logic.
>>
>> Martin
>>
>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [new] GNU emacs settings for clojure ?

[Bozhidar Batsov]

The "official" example config might be useful as well
https://github.com/clojure-emacs/example-config

On 15 June 2015 at 12:32, Josh Kamau  wrote:

> You could also try emacs-live  if you are an emacs beginner.
> https://github.com/overtone/emacs-live
>
> On Mon, Jun 15, 2015 at 9:32 AM, Jason Lewis 
> wrote:
>
>> M-x package-install cider should give you a better time.
>>
>> One is never "stuck" with emacs; one is privileged to enjoy it.
>>
>> On Sun, Jun 14, 2015, 18:01 Xavier  wrote:
>>
>>> Hello,
>>>
>>> I am new to clojure (which I really appreciate). I am stuck with GNU
>>> emacs for all the stuff I do and I cannot find something.
>>>
>>> I am playing with Composure, starting it using lein (ring server).
>>>
>>> Is there any possibility to do this directly via cider ? If not, how can
>>> I "connect" to it ?
>>>
>>> Regards
>>> --
>>>   Xavier
>>>   xav...@maillard.im
>>>
>>> --
>>> 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 new members are moderated - please be patient with
>>> your first post.
>>> To unsubscribe from this group, send email to
>>> clojure+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/clojure?hl=en
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to clojure+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>  --
>> 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 new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] CIDER 0.9

[Bozhidar Batsov]

Hey everyone,

CIDER 0.9 is finally out! You can read more about the release here
http://batsov.com/articles/2015/06/16/cider-0-dot-9/

Enjoy (responsibly)! :-)

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] CIDER 0.9

[Bozhidar Batsov]

Yeah, that's an unfortunate problem with package.el. See
https://github.com/clojure-emacs/cider/issues/1050#issuecomment-112595451

On 17 June 2015 at 05:38, Avi Avicenna  wrote:

> Wow!! Many thanks to all CIDER contributors.
>
> I didn't get it to work at first, but deleting all previous *.elc files
> and restarting emacs solves the problem.
>
> Congratulations!
>
> Yours,
> Avicenna
>
>
> On Tuesday, 16 June 2015 21:33:48 UTC+7, Bozhidar Batsov wrote:
>>
>> Hey everyone,
>>
>> CIDER 0.9 is finally out! You can read more about the release here
>> http://batsov.com/articles/2015/06/16/cider-0-dot-9/
>>
>> Enjoy (responsibly)! :-)
>>
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] CIDER 0.9

[Bozhidar Batsov]

Go do something useful with your IDE (or whatever) for a change and stop
trolling on this thread...

On 17 June 2015 at 16:56, Fluid Dynamics  wrote:

> On Wednesday, June 17, 2015 at 9:06:58 AM UTC-4, Leon Grapenthin wrote:
>>
>> Nevermind, I found the solution. (require 'cl) manually before compiling
>> cider.
>>
>>
>> On Wednesday, June 17, 2015 at 3:01:47 PM UTC+2, Leon Grapenthin wrote:
>>>
>>> I think I managed to get almost everything to work.
>>>
>>> The only thing that doesn't work is the nrepl history. When I hit M-p or
>>> M-n, I get
>>>
>>> Symbol's function definition is void: assert
>>>
>>> When I run (require 'cl) it changes to Invalid function: assert
>>>
>>> Am I the only one with this problem? Because I found no reports of it.
>>>
>>
> I must say, though, that every time something is upgraded it *is* quite
> amusing watching you emacs users running around chasing your tails for
> several hours afterwards while the rest of us are already getting useful
> work done. :)
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] CIDER 0.9

[Bozhidar Batsov]

Ouch. That's an oversight on my part. Seems we've used a few functions
straight from `cl` instead of the newer `cl-lib`. Thought I had all those
usages fixed, but I guess I haven't.

On 17 June 2015 at 16:06, Leon Grapenthin  wrote:

> Nevermind, I found the solution. (require 'cl) manually before compiling
> cider.
>
>
> On Wednesday, June 17, 2015 at 3:01:47 PM UTC+2, Leon Grapenthin wrote:
>>
>> I think I managed to get almost everything to work.
>>
>> The only thing that doesn't work is the nrepl history. When I hit M-p or
>> M-n, I get
>>
>> Symbol's function definition is void: assert
>>
>> When I run (require 'cl) it changes to Invalid function: assert
>>
>> Am I the only one with this problem? Because I found no reports of it.
>>
>> On Tuesday, June 16, 2015 at 4:33:48 PM UTC+2, Bozhidar Batsov wrote:
>>>
>>> Hey everyone,
>>>
>>> CIDER 0.9 is finally out! You can read more about the release here
>>> http://batsov.com/articles/2015/06/16/cider-0-dot-9/
>>>
>>> Enjoy (responsibly)! :-)
>>>
>>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] CIDER 0.9

[Bozhidar Batsov]

nREPL 0.2.6 is pretty old and has some serious bugs in it (alas there
hasn't been a lein release for a while). You'll have to pull in a newer
nREPL manually to get rid of this.

{:user {:dependencies [[org.clojure/tools.nrepl "0.2.10”]]}}

On 17 June 2015 at 10:04, Isaac Zeng  wrote:

> leiningen use org.clojure/tools.nrepl 0.2.6 cider-nrepl throw warning
>
>
> On Tuesday, June 16, 2015 at 10:33:48 PM UTC+8, Bozhidar Batsov wrote:
>>
>> Hey everyone,
>>
>> CIDER 0.9 is finally out! You can read more about the release here
>> http://batsov.com/articles/2015/06/16/cider-0-dot-9/
>>
>> Enjoy (responsibly)! :-)
>>
>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] CIDER 0.9

[Bozhidar Batsov]

Yeah, I'm aware of those problems, but as you already know they have to
fixed in leiningen. At least these days leiningen has an alternative (
https://github.com/boot-clj/boot).

On 18 June 2015 at 07:51, Alexis  wrote:

>
> Bozhidar Batsov  writes:
>
>  nREPL 0.2.6 is pretty old and has some serious bugs in it (alas there
>> hasn't been a lein release for a while). You'll have to pull in a newer
>> nREPL manually to get rid of this.
>>
>> {:user {:dependencies [[org.clojure/tools.nrepl "0.2.10”]]}}
>>
>
> Unfortunately this doesn't necessarily work - it certainly doesn't work
> for me! - as per the following:
>
> https://github.com/technomancy/leiningen/issues/1900
>
> https://github.com/technomancy/leiningen/issues/1901
>
>
> Alexis.
>
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> --- You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] CIDER 0.9

[Bozhidar Batsov]

Happy to hear this! :-)

On 18 June 2015 at 14:36, Stefan Kamphausen  wrote:

> Dear CIDER Devs,
>
>
> On Tuesday, June 16, 2015 at 4:33:48 PM UTC+2, Bozhidar Batsov wrote:
>>
>>
>> CIDER 0.9 is finally out! You can read more about the release here
>> http://batsov.com/articles/2015/06/16/cider-0-dot-9/
>>
>>
> thanks for the time and effort you've put into this!  Works fine for me.
> Update issues were totally minor so far.  Fixing them probably took less
> time than Eclipse needs to download the update information, let alone
> calculating dependencies. :-P
>
>
> Cheers,
> stefan
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] CIDER 0.9

[Bozhidar Batsov]

Submit a ticket + some repro steps and we'll have a look at it.

On 18 June 2015 at 15:55, Baishampayan Ghose  wrote:

> By the way, I just tried connecting to two different repls from the
> same project (the regular one + one started by fighweel) and it made
> my Emacs hang :-\
>
> Connecting to multiple repls on different projects works fine.
>
> Thanks,
> BG
>
> On Thu, Jun 18, 2015 at 5:26 PM, Bozhidar Batsov 
> wrote:
> > Happy to hear this! :-)
> >
> > On 18 June 2015 at 14:36, Stefan Kamphausen  wrote:
> >>
> >> Dear CIDER Devs,
> >>
> >>
> >> On Tuesday, June 16, 2015 at 4:33:48 PM UTC+2, Bozhidar Batsov wrote:
> >>>
> >>>
> >>> CIDER 0.9 is finally out! You can read more about the release here
> >>> http://batsov.com/articles/2015/06/16/cider-0-dot-9/
> >>>
> >>
> >> thanks for the time and effort you've put into this!  Works fine for me.
> >> Update issues were totally minor so far.  Fixing them probably took less
> >> time than Eclipse needs to download the update information, let alone
> >> calculating dependencies. :-P
> >>
> >>
> >> Cheers,
> >> stefan
> >
> >
> > --
> > 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 new members are moderated - please be patient with
> your
> > first post.
> > To unsubscribe from this group, send email to
> > clojure+unsubscr...@googlegroups.com
> > For more options, visit this group at
> > http://groups.google.com/group/clojure?hl=en
> > ---
> > You received this message because you are subscribed to the Google Groups
> > "Clojure" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to clojure+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Baishampayan Ghose
> b.ghose at gmail.com
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] CIDER 0.9

[Bozhidar Batsov]

You should definitely collect all this information in a bug report and
we'll track this issue down.

On 18 June 2015 at 17:32, Leon Grapenthin  wrote:

> Oh and you can also C-g and kill the unusubal REPL buffer if this happens.
>
>
> On Thursday, June 18, 2015 at 4:31:25 PM UTC+2, Leon Grapenthin wrote:
>>
>> Yeah, it usually happens when you start the second REPL while having the
>> REPL buffer open. It doesn't happen if you open the second REPL e. g. on
>> the project.clj...
>>
>> On Thursday, June 18, 2015 at 2:56:12 PM UTC+2, Baishampayan Ghose wrote:
>>>
>>> By the way, I just tried connecting to two different repls from the
>>> same project (the regular one + one started by fighweel) and it made
>>> my Emacs hang :-\
>>>
>>> Connecting to multiple repls on different projects works fine.
>>>
>>> Thanks,
>>> BG
>>>
>>> On Thu, Jun 18, 2015 at 5:26 PM, Bozhidar Batsov 
>>> wrote:
>>> > Happy to hear this! :-)
>>> >
>>> > On 18 June 2015 at 14:36, Stefan Kamphausen  wrote:
>>> >>
>>> >> Dear CIDER Devs,
>>> >>
>>> >>
>>> >> On Tuesday, June 16, 2015 at 4:33:48 PM UTC+2, Bozhidar Batsov wrote:
>>> >>>
>>> >>>
>>> >>> CIDER 0.9 is finally out! You can read more about the release here
>>> >>> http://batsov.com/articles/2015/06/16/cider-0-dot-9/
>>> >>>
>>> >>
>>> >> thanks for the time and effort you've put into this!  Works fine for
>>> me.
>>> >> Update issues were totally minor so far.  Fixing them probably took
>>> less
>>> >> time than Eclipse needs to download the update information, let alone
>>> >> calculating dependencies. :-P
>>> >>
>>> >>
>>> >> Cheers,
>>> >> stefan
>>> >
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups "Clojure" group.
>>> > To post to this group, send email to clo...@googlegroups.com
>>> > Note that posts from new members are moderated - please be patient
>>> with your
>>> > first post.
>>> > To unsubscribe from this group, send email to
>>> > clojure+u...@googlegroups.com
>>> > For more options, visit this group at
>>> > http://groups.google.com/group/clojure?hl=en
>>> > ---
>>> > You received this message because you are subscribed to the Google
>>> Groups
>>> > "Clojure" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> an
>>> > email to clojure+u...@googlegroups.com.
>>> > For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> Baishampayan Ghose
>>> b.ghose at gmail.com
>>>
>>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ANN: org.clojure/tools.namespace "0.2.11"

[Bozhidar Batsov]

Btw, what's the point of maintaining compatibility with 1.3? According to
the last state of Clojure survey pretty much no one uses 1.3 and 1.4 and
the upgrade path to 1.5 is not exactly hard...

On 20 June 2015 at 16:32, Magnar Sveen  wrote:

> Thanks! Have been waiting for this. Working with .cljc-files is quite nice
> after these changes. :)
>
>
> On Friday, June 19, 2015 at 9:46:08 PM UTC+2, Stuart Sierra wrote:
>>
>> tools.namespace: parse namespace declarations and reload
>> files in dependency order.
>>
>> https://github.com/clojure/tools.namespace
>>
>> Release 0.2.11 contains the following changes:
>>
>>   * [TNS-34] Support for reader conditionals
>>
>> tools.namespace still works only in Clojure(JVM), not
>> ClojureScript. But it is now able to parse both .clj files
>> and .cljc source files containing reader conditionals.
>>
>> This release of tools.namespace remains backwards-compatible
>> with older versions of Clojure back to 1.3.0.
>>
>>
>> Leiningen dependency information:
>> [org.clojure/tools.namespace "0.2.11"]
>>
>> This is a Clojure-contrib project,
>> http://dev.clojure.org/display/doc/Clojure+Contrib
>>
>> [TNS-34]: http://dev.clojure.org/jira/browse/TNS-34
>>
>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ANN: org.clojure/tools.namespace "0.2.11"

[Bozhidar Batsov]

Often compatibility comes at the cost of functionality and maintainability,
so in the end of the day someone has to pay the piper. Why would anyone be
using Emacs 23? It's easy to upgrade it pretty much everywhere and I doubt
anyone is doing much programming on their RHEL 5/6 production servers.

On 20 June 2015 at 18:24, Matching Socks  wrote:

> Hooray for compatibility in general.  Let us always remember the less
> fortunate.  (Ehem - users of Emacs 23 for example.)
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: CIDER + boot - how to make CIDER use installed version of cider-nrepl?

[Bozhidar Batsov]

Did you go through this https://github.com/boot-clj/boot/wiki/Cider-REPL ?

On 21 June 2015 at 11:20, Alexis  wrote:

>
> Hi all,
>
> Since the last leiningen release insists on using nREPL 0.2.6, i thought
> i'd have a go at using boot with CIDER instead.
>
> From what i can tell, boot has a similar issue to leiningen, in that the
> contents of ~/.boot/build.boot aren't respected by the boot REPL unless one
> starts the REPL from the ~/.boot directory. So, with my ~/.boot/build.boot
> file like this:
>
>(set-env!  :dependencies '[[org.clojure/tools.nrepl "0.2.10"]
> [cider/cider-nrepl "0.9.1-SNAPSHOT"]])
> if i do:
>
>$ cd ~
>$ boot repl
>
> i get:
>
>nREPL server started on port 42018 on host 127.0.0.1 -nrepl://
> 127.0.0.1:42018 REPL-y 0.3.5, nREPL 0.2.8 Clojure1.6.0 OpenJDK 64-Bit
> Server VM 1.7.0_79-b14
>
> whereas if i do:
>
>$ cd ~/.boot/
>$ boot repl
>
> i get:
>
>nREPL server started on port 37924 on host 127.0.0.1 -nrepl://
> 127.0.0.1:37924 REPL-y 0.3.5, nREPL 0.2.10 Clojure1.6.0 OpenJDK
> 64-Bit Server VM 1.7.0_79-b14
>
> Nonetheless, if in Emacs i run `cider-jack-in`, i get:
>
>; CIDER 0.9.1snapshot (package: 20150618.2308) (Java 1.7.0_79,
> Clojure 1.6.0, nREPL 0.2.10) WARNING: The following requirednREPL ops
> are not supported:  apropos classpath complete eldocformat-code
> format-edn info inspect-pop inspect-pushinspect-refresh macroexpand
> ns-list ns-vars ns-path refreshresource stacktrace toggle-trace-var
> toggle-trace-ns undefPlease, install (or update) cider-nrepl
> 0.9.1-SNAPSHOT andrestart CIDER
>
> So okay, CIDER is picking up the 0.2.10 version of nREPL - good. But the
> message:
>
>Please, install (or update) cider-nrepl 0.9.1-SNAPSHOT andrestart
> CIDER
>
> is odd, given that my system has:
>
>~/.m2/repository/cider/cider-nrepl/0.9.1-SNAPSHOT/_maven.repositories
>
> ~/.m2/repository/cider/cider-nrepl/0.9.1-SNAPSHOT/cider-nrepl-0.9.1-20150619.062729-1.jar
>
> ~/.m2/repository/cider/cider-nrepl/0.9.1-SNAPSHOT/cider-nrepl-0.9.1-20150619.062729-1.jar.sha1
>
> ~/.m2/repository/cider/cider-nrepl/0.9.1-SNAPSHOT/cider-nrepl-0.9.1-20150619.062729-1.pom
>
> ~/.m2/repository/cider/cider-nrepl/0.9.1-SNAPSHOT/cider-nrepl-0.9.1-20150619.062729-1.pom.sha1
>
> ~/.m2/repository/cider/cider-nrepl/0.9.1-SNAPSHOT/cider-nrepl-0.9.1-SNAPSHOT.jar
>
> ~/.m2/repository/cider/cider-nrepl/0.9.1-SNAPSHOT/cider-nrepl-0.9.1-SNAPSHOT.pom
>
> ~/.m2/repository/cider/cider-nrepl/0.9.1-SNAPSHOT/maven-metadata-clojars.xml
>
> ~/.m2/repository/cider/cider-nrepl/0.9.1-SNAPSHOT/maven-metadata-clojars.xml.sha1
>
> ~/.m2/repository/cider/cider-nrepl/0.9.1-SNAPSHOT/resolver-status.properties
>
> What am i doing wrong, such that cider-nrepl 0.9.1-SNAPSHOT is definitely
> available, but CIDER can't find it / make use of it?
>
>
> Alexis.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> --- You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cider form-init buffer

[Bozhidar Batsov]

When exactly does this appear? It's just a file used by Clojure for code
evaluated in a REPL, but shouldn't appear in CIDER at all (except in
stacktraces).

On 23 June 2015 at 18:56, dtouch3d completely  wrote:

> Is there a way to disable the /tmp/form-init*.clj buffer from showing when
> there is an error in evaluation ?  It can be very annoying as I am new to
> clojure and emacs and it replaces my source file buffer and provides no
> useful information. The cider-error buffer is more than adequate for
> understanding the error.
>
> Thanks.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cider form-init buffer

[Bozhidar Batsov]

Submit a ticket to the issue tracker with some repro steps and I'll take a
look at it. I've never seen this behaviour (and nobody has reported it so
far), so I'm guessing something in your setup is uncommon.

On 23 June 2015 at 21:27, dtouch3d completely  wrote:

> It appears when I try to evaluate code that has syntactic errors.
>
> On Tuesday, June 23, 2015 at 7:42:10 PM UTC+3, Bozhidar Batsov wrote:
>>
>> When exactly does this appear? It's just a file used by Clojure for code
>> evaluated in a REPL, but shouldn't appear in CIDER at all (except in
>> stacktraces).
>>
>> On 23 June 2015 at 18:56, dtouch3d completely  wrote:
>>
>>> Is there a way to disable the /tmp/form-init*.clj buffer from showing
>>> when there is an error in evaluation ?  It can be very annoying as I am new
>>> to clojure and emacs and it replaces my source file buffer and provides no
>>> useful information. The cider-error buffer is more than adequate for
>>> understanding the error.
>>>
>>> Thanks.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To post to this group, send email to clo...@googlegroups.com
>>> Note that posts from new members are moderated - please be patient with
>>> your first post.
>>> To unsubscribe from this group, send email to
>>> clojure+u...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/clojure?hl=en
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to clojure+u...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] CIDER 0.9.1

[Bozhidar Batsov]

Hi everyone,

CIDER 0.9.1 (codename “EuroCIDER”) is out! The release notes are here
https://github.com/clojure-emacs/cider/releases/tag/v0.9.1

This release fixes pretty much all serious issues that were discovered
shortly after 0.9.0 went
live and (as you probably have guessed by now) is dedicated to EuroClojure.
Enjoy EuroClojure and EuroCIDER!

For me it's time to start packing for my flight. See you at Barcelona!

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: cider-error go to line

[Bozhidar Batsov]

This is a problem on nREPL, not CIDER. See
http://dev.clojure.org/jira/browse/NREPL-59 for details.

There aren't any real solutions to this, other than fixing nREPL, but we're
considering some workarounds (e.g. trying to find the definition using a
regular expression and using the relative position from there)
https://github.com/clojure-emacs/cider/issues/1175

But as I said NREPL-59 has to be fixed eventually, as this is killing us
(and everyone using nREPL), so consider dropping by the issue and voicing
your support for the proposed patch.

On 3 July 2015 at 02:44, Ritchie Cai  wrote:

> When I get a cider-error, it tells me line number within the function that
> raised the error, but is there an easy way to go to that line?
> Since the line number is within the function, I've been counting lines
> manually at the moment ... getting tired of this.
>
> Anyone has any suggestions?
>
> Thanks
> Ritchie
>
>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: #{:rant} Questions about contribution policy and clojure compiler source.

[Bozhidar Batsov]

On 18 July 2015 at 14:13, Andrey Antukh  wrote:

> Hi!
>
> I have some, maybe controversial, questions...
>
> A little bit of context:
> https://twitter.com/aphyr/status/621806683908542464
>
> Why this is like a normal approach for managing third party contributions
> to clojure core? This kind of things the only discourages the
> contributions. Maybe I don't have more context about this concrete case,
> but seems is not a unique.
> And in general, I have the perception that the clojure development process
> is a little bit opaque...
>

Many people feel this way, but ultimately Clojure is Rich's project and I
guess Cognitect's to some extent. If they don't want to run it like other
more open & contribution-friendly OSS projects this is obviously their
right.


>
> An other question: Why the great amount of clojure compiler code has no
> indentation style and bunch of commented code.
>
> It is indented like a freshman. Sorry, I don't want offend any one, but
> eyes hurt when reading the code compiler clojure (obviously I'm speaking
> about the look and feel, and no the quality of the code).
>
> Some examples:
>
> Indentation (or maybe no indentation):
>
> https://github.com/clojure/clojure/blob/36d665793b43f62cfd22354aced4c6892088abd6/src/jvm/clojure/lang/APersistentVector.java#L86
>
> Bunch of commented code and also no indentation:
>
> https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/AMapEntry.java#L60
>
> If you compare some clojure compiler code with different code snippets
> from other languages, the indentation is clearly more cared:
>
> Kotlin:
> https://github.com/JetBrains/kotlin/blob/master/core/descriptors/src/org/jetbrains/kotlin/types/AbstractClassTypeConstructor.java#L44
> Rust:
> https://github.com/rust-lang/rust/blob/master/src/libstd/io/buffered.rs#L165
> Ceylon:
> https://github.com/ceylon/ceylon-compiler/blob/master/src/com/redhat/ceylon/compiler/java/codegen/AttributeDefinitionBuilder.java#L233
>
> This is a random list of code snippets from different compilers with
> indentation that is more human friendly.
>
> I don't intend judge any one, but when a I learn Clojure compiler I expect
> something different. I expect something more carefully done.
>
> No body thinks the same thing that me?
>


This topic resurfaces all the time. I'd certainly like to see the Java code
"fixed", as its layout is highly unidiomatic (not to mention somewhat
confusing).
I doubt this will happen though - seems Rich doesn't think this is a big
problem and AFAIK he's concerned that fixing the layout will affect
currently submitted patches. Knowing all the hoops one has to jump to get a
patch into Clojure, this doesn't sound like a pretty strong argument, but
once again - his project, his rules. People seem to undervalue the value of
polish in a project, as good style and overall tidiness set apart the good
from the great.


>
> I think that have a sane, more open contribution policy, with clear and
> more cared code formatting, is not very complicated thing and is going to
> favor the clojure and its community.
>

Certainly. As far basic things go, I think it's also discouraging to see
commit messages like:

* tuples
* tuning tuples
* tuning tuples
* fix

And don't get me started on commented out code and Javadoc/Clojure
docstrings. It'd be nice if at least improvements of cosmetic nature where
easier to contribute, but alas - this also doesn't seem likely to happen.



>
> Andrey
> --
> Andrey Antukh - Андрей Антух - 
> http://www.niwi.nz
> https://github.com/niwinz
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: #{:rant} Questions about contribution policy and clojure compiler source.

[Bozhidar Batsov]

Btw, here's a bit more colour on the inclusion of tuples, Zack's own 
thoughts on the subject 
https://gist.github.com/ztellman/9ded0b77281f48942b68


On Saturday, July 18, 2015 at 2:14:02 PM UTC+3, Andrey Antukh wrote:
>
> Hi!
>
> I have some, maybe controversial, questions...
>
> A little bit of context: 
> https://twitter.com/aphyr/status/621806683908542464 
>
> Why this is like a normal approach for managing third party contributions 
> to clojure core? This kind of things the only discourages the 
> contributions. Maybe I don't have more context about this concrete case, 
> but seems is not a unique.
> And in general, I have the perception that the clojure development process 
> is a little bit opaque... 
>
> An other question: Why the great amount of clojure compiler code has no 
> indentation style and bunch of commented code. 
>
> It is indented like a freshman. Sorry, I don't want offend any one, but 
> eyes hurt when reading the code compiler clojure (obviously I'm speaking 
> about the look and feel, and no the quality of the code).
>
> Some examples:
>
> Indentation (or maybe no indentation):
>
> https://github.com/clojure/clojure/blob/36d665793b43f62cfd22354aced4c6892088abd6/src/jvm/clojure/lang/APersistentVector.java#L86
>
> Bunch of commented code and also no indentation:
>
> https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/AMapEntry.java#L60
>
> If you compare some clojure compiler code with different code snippets 
> from other languages, the indentation is clearly more cared:
>
> Kotlin: 
> https://github.com/JetBrains/kotlin/blob/master/core/descriptors/src/org/jetbrains/kotlin/types/AbstractClassTypeConstructor.java#L44
> Rust: 
> https://github.com/rust-lang/rust/blob/master/src/libstd/io/buffered.rs#L165
> Ceylon: 
> https://github.com/ceylon/ceylon-compiler/blob/master/src/com/redhat/ceylon/compiler/java/codegen/AttributeDefinitionBuilder.java#L233
>
> This is a random list of code snippets from different compilers with 
> indentation that is more human friendly.
>
> I don't intend judge any one, but when a I learn Clojure compiler I expect 
> something different. I expect something more carefully done.
>
> No body thinks the same thing that me? 
>
> I think that have a sane, more open contribution policy, with clear and 
> more cared code formatting, is not very complicated thing and is going to 
> favor the clojure and its community.
>
> Andrey
> -- 
> Andrey Antukh - Андрей Антух - >
> http://www.niwi.nz
> https://github.com/niwinz
>  

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: #{:rant} Questions about contribution policy and clojure compiler source.

[Bozhidar Batsov]

On 18 July 2015 at 18:44, Luc Prefontaine 
wrote:

> Sure, indentation is what gets the code running on metal :))
>

That remark is wrong on so many levels...

In the words of the legendary SICP authors - "Programs must be written for
people to read, and only incidentally for machines to execute."


>
> Not ranting here, just my abs dying from the pain as I laugh :))
>
> As for the contrib process, go have a look at Linux. You'll be happy that
> Rich is cool by every meaning of the word.
>

I've been involved in many OSS project and certainly there are projects
where the contribution process is worse than Clojure's. I do believe,
however, that pointing that things could be worse in not the right
attitude. There's always room for improvement.


>
> There's this misconception about open source that we should all wear
> flower collars and sing Kumbaya. Mostly a 60's view of human collaboration.
>
> That ain't the way to get it done.
> It works for ants and termites, they work as groups but we are human
> beings with our strong individuality.
>
> Some form of central control is needed. Opposed by traction from some
> individuals that would like to move faster or in other directions.
>

Central control is not the same as dictator. It's not uncommon for projects
to have several "leaders". Sure, having less people on the top makes it
easier to make decisions, but it also makes it easier to make mistakes (not
to mention it creates bottlenecks here and there).


>
> This is ok but not at the expense of the cohesion of the end result.
>
> Hence this tensed balance.
>
> Rich created Clojure, he knows were he wants to go with it. Any ideas we
> bring in the process is evaluated. However not all of them make sense or
> are worth the effort to implement.
>

> Aside from our respective ego being hurt because our ideas are not
> retained or our contribs vetted in the first pass there's little damage
> done.
>

I doubt anyone thinks something like this is a big problem. After all it's
common for some ideas to be shot down and complex ideas require a lot of
time to reach maturity. If there's something I dislike it's that sometimes
important bugfixes are delayed for quite a while. Especially in the absense
of bugfix releases.


>
> If it was not the case Clojure would have zero traction and Linux
> likewise. Search for Linus rants about contributors and try to relate this
> with the level of success of Linux.
>
> They are not so many open source projects that have the same stability
> from release to release as Clojure or Linux.
>

You're comparing apples to oranges here. Linux is not a one-man show - most
subsystems have their own maintainers and Linus monitors the development
there only cursory. Not to mention there's no company acting as the steward
of the language. I'm not saying one of the approaches is better/worse, I'm
just saying that's a poor base for such a comparison.


>
> Control and absence of complacency are key factors to achieve this kind of
> success.
>
> Luc P.
>
> Sent from my iPhone
>
> On Jul 18, 2015, at 07:13, Andrey Antukh  wrote:
>
> Hi!
>
> I have some, maybe controversial, questions...
>
> A little bit of context:
> https://twitter.com/aphyr/status/621806683908542464
>
> Why this is like a normal approach for managing third party contributions
> to clojure core? This kind of things the only discourages the
> contributions. Maybe I don't have more context about this concrete case,
> but seems is not a unique.
> And in general, I have the perception that the clojure development process
> is a little bit opaque...
>
> An other question: Why the great amount of clojure compiler code has no
> indentation style and bunch of commented code.
>
> It is indented like a freshman. Sorry, I don't want offend any one, but
> eyes hurt when reading the code compiler clojure (obviously I'm speaking
> about the look and feel, and no the quality of the code).
>
> Some examples:
>
> Indentation (or maybe no indentation):
>
> https://github.com/clojure/clojure/blob/36d665793b43f62cfd22354aced4c6892088abd6/src/jvm/clojure/lang/APersistentVector.java#L86
>
> Bunch of commented code and also no indentation:
>
> https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/AMapEntry.java#L60
>
> If you compare some clojure compiler code with different code snippets
> from other languages, the indentation is clearly more cared:
>
> Kotlin:
> https://github.com/JetBrains/kotlin/blob/master/core/descriptors/src/org/jetbrains/kotlin/types/AbstractClassTypeConstructor.java#L44
> Rust:
> https://github.com/rust-lang/rust/blob/master/src/libstd/io/buffered.rs#L165
> Ceylon:
> https://github.com/ceylon/ceylon-compiler/blob/master/src/com/redhat/ceylon/compiler/java/codegen/AttributeDefinitionBuilder.java#L233
>
> This is a random list of code snippets from different compilers with
> indentation that is more human friendly.
>
> I don't intend judge any one, but when a I learn Clojure compiler I expect
> something different. 

Re: #{:rant} Questions about contribution policy and clojure compiler source.

[Bozhidar Batsov]

On 18 July 2015 at 18:48, Colin Yates  wrote:

> +1 (although I maybe wouldn’t be so mocking in my tone ;-). Since when did
> software design by committee work; anyone remember J2EE? (and yes, that
> does deserve my mocking tone).
>

Why do people always say that a committee is the only alternative of having
a BDFL? That's clearly not the case. Would it be so bad of Alex Miller had
the power to vet and merge certain clear-cut things himself? Or someone
else like him? While create artificial bottlenecks when we can do without
them?

>
> I have no idea about the details being discussed here/why people’s noses
> are out of joint, but I can think of as many success with a single overlord
> in place as there are failures caused by political infighting.
>
> On 18 Jul 2015, at 16:44, Luc Prefontaine 
> wrote:
>
> Sure, indentation is what gets the code running on metal :))
>
> Not ranting here, just my abs dying from the pain as I laugh :))
>
> As for the contrib process, go have a look at Linux. You'll be happy that
> Rich is cool by every meaning of the word.
>
> There's this misconception about open source that we should all wear
> flower collars and sing Kumbaya. Mostly a 60's view of human collaboration.
>
> That ain't the way to get it done.
> It works for ants and termites, they work as groups but we are human
> beings with our strong individuality.
>
> Some form of central control is needed. Opposed by traction from some
> individuals that would like to move faster or in other directions.
>
> This is ok but not at the expense of the cohesion of the end result.
>
> Hence this tensed balance.
>
> Rich created Clojure, he knows were he wants to go with it. Any ideas we
> bring in the process is evaluated. However not all of them make sense or
> are worth the effort to implement.
>
> Aside from our respective ego being hurt because our ideas are not
> retained or our contribs vetted in the first pass there's little damage
> done.
>
> If it was not the case Clojure would have zero traction and Linux
> likewise. Search for Linus rants about contributors and try to relate this
> with the level of success of Linux.
>
> They are not so many open source projects that have the same stability
> from release to release as Clojure or Linux.
>
> Control and absence of complacency are key factors to achieve this kind of
> success.
>
> Luc P.
>
> Sent from my iPhone
>
> On Jul 18, 2015, at 07:13, Andrey Antukh  wrote:
>
> Hi!
>
> I have some, maybe controversial, questions...
>
> A little bit of context:
> https://twitter.com/aphyr/status/621806683908542464
>
> Why this is like a normal approach for managing third party contributions
> to clojure core? This kind of things the only discourages the
> contributions. Maybe I don't have more context about this concrete case,
> but seems is not a unique.
> And in general, I have the perception that the clojure development process
> is a little bit opaque...
>
> An other question: Why the great amount of clojure compiler code has no
> indentation style and bunch of commented code.
>
> It is indented like a freshman. Sorry, I don't want offend any one, but
> eyes hurt when reading the code compiler clojure (obviously I'm speaking
> about the look and feel, and no the quality of the code).
>
> Some examples:
>
> Indentation (or maybe no indentation):
>
> https://github.com/clojure/clojure/blob/36d665793b43f62cfd22354aced4c6892088abd6/src/jvm/clojure/lang/APersistentVector.java#L86
>
> Bunch of commented code and also no indentation:
>
> https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/AMapEntry.java#L60
>
> If you compare some clojure compiler code with different code snippets
> from other languages, the indentation is clearly more cared:
>
> Kotlin:
> https://github.com/JetBrains/kotlin/blob/master/core/descriptors/src/org/jetbrains/kotlin/types/AbstractClassTypeConstructor.java#L44
> Rust:
> https://github.com/rust-lang/rust/blob/master/src/libstd/io/buffered.rs#L165
> Ceylon:
> https://github.com/ceylon/ceylon-compiler/blob/master/src/com/redhat/ceylon/compiler/java/codegen/AttributeDefinitionBuilder.java#L233
>
> This is a random list of code snippets from different compilers with
> indentation that is more human friendly.
>
> I don't intend judge any one, but when a I learn Clojure compiler I expect
> something different. I expect something more carefully done.
>
> No body thinks the same thing that me?
>
> I think that have a sane, more open contribution policy, with clear and
> more cared code formatting, is not very complicated thing and is going to
> favor the clojure and its community.
>
> Andrey
> --
> Andrey Antukh - Андрей Антух - 
> http://www.niwi.nz
> https://github.com/niwinz
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscrib

Re: #{:rant} Questions about contribution policy and clojure compiler source.

[Bozhidar Batsov]

On 18 July 2015 at 20:18, Luc Prefontaine 
wrote:

> Aaah ! The pull request looms again :)
>
> A bug tracking system is essentialy to coordinate efforts, pull request
> are not a mechanism to track fixes/improvements and discuss about
> them. That may work for a very small team. The # of clojure contributors
> far excess that size.
>

So, Ruby on Rails is a small project, right? And if we have many
contributors we should show no respect for their time - we should actually
make it harder to contribute, so it'd be easier on us, right?


>
> Pull requests/gitbhub issues are used by Clojure library maintainers
> outside of the core,
>  their respective contributor team size makes this usable.
>
> Choosing one tracking system is a feat by itself, Jira does everything
> albeit it may be a beast to configure.
> I think that the choice of Jira predates moving the Clojure code from
> google to github but I may be wrong.
> The github tracking system was not at par with Jira features at that time
> anyway.
>

Many projects predate GitHub, yet they eventually adopted it. And it's
never about GitHub in particular - it's only about making things efficient
and pleasant for everyone involved. I work with JIRA for a living and my
team mostly hates it, I can only imagine the willingness of casual
contributors to deal with it. How do you do an inline patch review in JIRA?
How do you update patches automatically? It's never about particular tools,
it's all about making smart choices.


>
> Once that choice is done, moving out to something else requires a
> significant effort, you need to pull all this history you built about
> your software into your new bug tracking solution. You can't loose this,
> it's your software collective memory.
>
> All this discussion around pull request IMO is more an expression of human
> lazyness. Having to document is always seen as a
> chore by most developpers. ‎This is not an arcane human trait, it has been
> known for decades.
>

Laziness? Time is our most important resource and we should always be
mindful of the time people have to invest (waste) to contribute to our
projects. For me lowering the bar to entry is the same as respecting the
time of the person on the other end of the ticket/patch/whatever. If you
take a look at my profile on GitHub you'll see I maintain a few projects
and I go to great lengths to make sure all the projects are inviting and
it's easy for people to start a conversation or pitch in. This pays off big
time in the long run.


>
> Anything else requires a discussion forum if you want to maintain a
> minimal level of quality and allow some discussions around the issue being
> fixed
> in a large team effort/critical piece of software. A mailing list is not
> at par with a bug tracking system in this regard.
>
> Curiously, linux has a bug tracking system and people submit patches or
> links are made to patches.
> Take a walk on launchpad.
>

Curiously, most of the people who work on Linux are on the payroll of a
corporation like Red Hat. If I was getting paid to do something,
I'd definitely be more willing to through more hurdles - after all that's
part of my job, right?


>
> No serious software business would drive their dev without a tracking
> system. Open source projects are no
> different if they want to attain some level of success. If critical open
> source is to be used by businesses, it has to
> play with similar tools. Clojure too me is critical to my business and to
> many others. It cannot fail on us.
> It would be like building pyramids on moving sand.
>
> Again there's no Kumbaya song playing here.
>
> As a last note, Alex Miller must dream about the emails exchanged on the
> mailing list.
> Suggestions are certainly looked upon and discussed upstream. It does not
> mean that they will be considered
> worth to investigate/implement or they may come out differently (that ego
> thing looming again).
>

Alex is an amazing fellow, there's no denying this. I only wish we could
clone him somehow. :-)


>
> +1 for Jira and patches.
>
> Luc P.
>
>
>
> On Sat, 18 Jul 2015 19:05:16 +0300
> Andrey Antukh  wrote:
>
> > On Sat, Jul 18, 2015 at 6:48 PM, Colin Yates 
> > wrote:
> >
> > > +1 (although I maybe wouldn’t be so mocking in my tone ;-). Since
> > > when did software design by committee work; anyone remember J2EE?
> > > (and yes, that does deserve my mocking tone).
> > >
> > > I have no idea about the details being discussed here/why people’s
> > > noses are out of joint, but I can think of as many success with a
> > > single overlord in place as there are failures caused by political
> > > infighting.
> > >
> >
> > In general, I'm pretty happy with the "benevolent dictator" approach.
> > But some openness would be awesome. As first think that comes in my
> > mind is: have a clear roadmap for Clojure and its core libraries such
> > as core.async.
> >
> > Some channel for requesting features, and the ability to know a
> > opinion of the clojure core team about

Re: #{:rant} Questions about contribution policy and clojure compiler source.

[Bozhidar Batsov]

On 18 July 2015 at 22:52, Luc Préfontaine 
wrote:

> Each linux kernel release involves hundreds of people.
> Many release had above a thousand contributors.
> This is for your enlightenment and are old figures:
>
> http://royal.pingdom.com/2012/04/16/linux-kernel-development-numbers/
>

Did you even read this article? "75% – The share of all kernel development
that is done by developers who are being paid for their work."
This doesn't exactly contract what I said.


>
> There are as many people not officially hired to work for linux operating
> system
> focused businesses that submit patches through the ticketing system.
>
> As for the development lifecycle of the linux kernel:
> http://www.linuxfoundation.org/content/22-lifecycle-patch
>
> You can read the other sections, if you find the Clojure dev. lifecycle
> arcane, you will
> freak at this one.
> Obviously, these guys must all be old fashion outdated folks in this era
> of instant
> communication and snapchat like media, there's no other explanation for
> such a
> bureaucratic process :)
>
> How much pain is it to upgrade to a new Clojure version ? Nil.
> How much pain is it to upgrade to a new linux kernel ?
> Not nil but considering the size of this project, its ramifications and
> the hardware
> changing every 6 months, not big. On par with Clojure I would say.
>
> How much pain to upgrade to a new version of Ruby on Rails ?
> Huge. I know, I have been through this a number of times. Not just major
> releases, even maintenance ones are a nightmare to upgrade.
>
> Disclaimer: I am not saying that Rails has a bad lifecycle, I am just
> stating feedback
> from me and other people that actually lived this. Gee, I sound like
> Mallard Fillmore...
>
> That's for the political correctness of this post. And to avoid being
> harassed, sued, whatever.
>
> I would like us to compare carrots with carrots, not with apples or
> strawberries but if
> you insist
>
> To me the result is utterly important.
> We deliver 24/7 software under linux using Clojure. We have up times of
> more than 300 days. One upgrade a year. This is the world that live into.
>
> Making it 'harder to contribute' like you state is the price to pay for
> some form of
> quality control. Contributing to something that eventually crumbles
> because of a
> lack of QA is of no value. To us all.
>
> Stuart has made this evaluation. Since it models by some aspect how a
> successful
> project like Linux is managed, I find it hard to throw a stone at the
> current lifecycle.
>
> That may look to you as an ultra-conservative approach. Let's put it this
> way,
> I would use Linux and Clojure to control a nuclear plant anytime.
>
> I am quite certain sure I would not use Rails or Ruby for this purpose.
>

As this conversation isn't really going anywhere I'll keep my thoughts to
myself.


>
> Luc P.
>
>
> Luc P.
>
> Sent from my iPad
>
> On Jul 18, 2015, at 14:32, Bozhidar Batsov  wrote:
>
> On 18 July 2015 at 20:18, Luc Prefontaine 
> wrote:
>
>> Aaah ! The pull request looms again :)
>>
>> A bug tracking system is essentialy to coordinate efforts, pull request
>> are not a mechanism to track fixes/improvements and discuss about
>> them. That may work for a very small team. The # of clojure contributors
>> far excess that size.
>>
>
> So, Ruby on Rails is a small project, right? And if we have many
> contributors we should show no respect for their time - we should actually
> make it harder to contribute, so it'd be easier on us, right?
>
>
>>
>> Pull requests/gitbhub issues are used by Clojure library maintainers
>> outside of the core,
>>  their respective contributor team size makes this usable.
>>
>> Choosing one tracking system is a feat by itself, Jira does everything
>> albeit it may be a beast to configure.
>> I think that the choice of Jira predates moving the Clojure code from
>> google to github but I may be wrong.
>> The github tracking system was not at par with Jira features at that time
>> anyway.
>>
>
> Many projects predate GitHub, yet they eventually adopted it. And it's
> never about GitHub in particular - it's only about making things efficient
> and pleasant for everyone involved. I work with JIRA for a living and my
> team mostly hates it, I can only imagine the willingness of casual
> contributors to deal with it. How do you do an inline patch review in JIRA?
> How do you update patches automatically? It's never about particular tools,
> it's all about making smart choices.
>
>
>>
>> O

Re: [:ann :book] ClojureScript Unraveled

[Bozhidar Batsov]

That's a really exciting project, as a lot of people are looking to get
started with ClojureScript and are finding it kind of hard because of the
lack of such resources.

My advise would be to put a bit heavier focus on the differences between
Clojure & ClojureScript and add some section about setting up various
editors/IDEs.
A chapter like "ClojureScript for Clojure devs" would be great IMO.


On 20 July 2015 at 00:51, Alejandro Gómez  wrote:

>  We just released the second revision which includes a lot of
> corrections, an Acknowledgments section and an almost finished chapter
> about CSP & core.async which covers all its API and introduces the CSP
> concepts.
>
>
> - Leanpub: https://leanpub.com/clojurescript-unraveled
> - GitHub repository: https://github.com/funcool/clojurescript-unraveled
> - HTML version: http://funcool.github.io/clojurescript-unraveled/
>
>
> On Sun, Jul 19, 2015, at 14:51, Nando Breiter wrote:
>
> I'm a Clojure beginner and wanted to compliment the authors on a very
> clear yet concise text. Thank you.
>
>
> Thanks a lot, any feedback will be greatly appreciated since one of the
> goals of the project is to make ClojureScript accesible to newcomers.
>
>
>
>
>
> Aria Media Sagl
> Via Rompada 40
> 6987 Caslano
> Switzerland
>
> +41 (0)91 600 9601
> +41 (0)76 303 4477 cell
> skype: ariamedia
>
> On Fri, Jul 17, 2015 at 7:30 PM, Alejandro Gómez 
> wrote:
>
> Hello everybody,
>
>  I'm happy to announce that Andrey Antoukh (@niwinz) and I published the
>  book about ClojureScript
>  that we have been writing lately on Leanpub. It's not still 100%
>  complete but the sections about
>  the language and compiler are almost done. We'd greatly appreciate any
>  feedback, errata or suggestions
>  for the book.
>
>  It is an open source book licensed under a Creative Commons BY-SA
>  license and will forever remain
>  free and open to community participation. Publishing it on Leanpub is a
>  convenient way for readers
>  to be notified whenever a new release comes out and not to go through
>  the process of generating the
>  book themselves. If you feel like it and can afford it you can make a
>  donation and buy us a beer too!
>
>  - Leanpub: https://leanpub.com/clojurescript-unraveled
>  - GitHub repository: https://github.com/funcool/clojurescript-unraveled
>  - HTML version: http://funcool.github.io/clojurescript-unraveled/
>
>  Yours,
>
>  Alejandro
>
>  --
>  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 new members are moderated - please be patient with
> your first post.
>  To unsubscribe from this group, send email to
>  clojure+unsubscr...@googlegroups.com
>  For more options, visit this group at
>  http://groups.google.com/group/clojure?hl=en
>  ---
>  You received this message because you are subscribed to the Google Groups
> "Clojure" group.
>  To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
>  For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
>  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 new members are moderated - please be patient with
> your first post.
>  To unsubscribe from this group, send email to
>  clojure+unsubscr...@googlegroups.com
>  For more options, visit this group at
>  http://groups.google.com/group/clojure?hl=en
>  ---
>  You received this message because you are subscribed to the Google Groups
> "Clojure" group.
>  To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
>  For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google

Re: #{:rant} Questions about contribution policy and clojure compiler source.

[Bozhidar Batsov]

True that. While I'd prefer a more common indentation style to be adopted,
I'd definitely settle just for Rich's style being applied consistently
everywhere.
Trying to account for indentation inconsistencies when working on a patch
is not fun at all. So yeah - the real problems about the formatting are:

* inconsistent indentation
* mixing tabs & spaces
* trailing whitespace (although I guess it's ok to kill it in our patches)

The style itself is up to the project's author and of no big importance by
itself.


On 20 July 2015 at 17:08, Colin Fleming  wrote:

> Leaving aside your usual "humour", you are once again setting up a total
> strawman. Nicola did not say that maintenance should be as much fun as
> writing new code, nor did he propose rewriting anything. He made a very
> specific claim - that contributing to the Clojure codebase is much less
> pleasant than it could be, not because the indentation style is unusual but
> because it is inconsistent.
>
> Since he has a long history of writing very high quality patches for
> Clojure whereas you, as far as I can tell, have never written any, means
> that his opinion holds a lot more weight in this discussion, for me at
> least.
>
> On 20 July 2015 at 14:45, Luc Prefontaine 
> wrote:
>
>>
>> --- advanced warning: the following section contains a lethal form of
>> irony, please skip it if your health condition does not tolerate irony ---
>>
>> Sure and I never maintained code written by others in 30 years... Never
>> wrote patches, never had to comply with odd indentation habits.
>> I am an absolute newbie on that subject.
>>
>> I always write new code and leave maintenance to other less fortunate
>> people.
>>
>> --- end of ironic section ---
>>
>> I agree with you. Totally.
>>
>> Maintenance has never been funnier than new dev and will never be.
>>
>> Day to day maintenance specifically is a pain in the ass.
>>
>> Preemptive rewrites as part of maintenance is doable when the code
>> reaches an unbearable state
>> but someone in charge has to call the shots.
>>
>> I had numerous discussions about rewriting in the last few decades and
>> yes patch consistency is always brought forward.
>>
>> The driving factors around a decision like this are: the life expectancy
>> of the code vs it's complexity vs maintenance cost and agility vs risks
>> involved in a rewrite vs budget vs accumulated knowledge.
>>
>> The maintainer's pain is not the only factor taken into account and often
>> not the most important.
>>
>> That's the harsh reality of life.
>>
>> Ideally we would always write new stuff and trash  code every 2/3 years
>> to keep our mood at its peak.
>>
>> Life is not like that. Sorry :)
>>
>> Sent from my iPhone
>>
>> > On Jul 20, 2015, at 08:14, Nicola Mometto  wrote:
>> >
>> > I take it you have never worked on a patch for clojure.
>> > I have, and I can tell you that it's not the indentation style the
>> > issue -- everybody likes his own and it's definitely in the
>> > maintainer's rights to chose what indentation style should be used and
>> > for contributors to adapt, I don't have a problem with that.
>> > I have a problem with the fact that the indentation style is not
>> > consistent even between lines of the same method, tabs and spaces are
>> > mixed everywhere -- for every non trivial patch I submit I have to
>> > spend non trivial amounts of time to reindent my code using spaces or
>> > tabs where appropriate to be consistent with the surrounding code and
>> > making sure I don't accidentally commit whitespace changes in my
>> > patches.
>> > It's certainly not the biggest issue (not even close to it) in the
>> > contributing process, but it definitely is an issue and it doesn't
>> > help making the overall contributing experience a pleasant one, or one
>> > would want to repeat.
>> >
>> > And the claim that no indentation fix can happen to avoid breaking
>> > existing patches in jira is frankly laughable. With the amount of time
>> > that usually passes between the writing of a patch and its application
>> > to the code base, a lot of them already need to be rebased/rewritten
>> > to apply cleanly, often multiple times.
>> >
>> > On Sat, Jul 18, 2015 at 5:44 PM, Luc Prefontaine
>> >  wrote:
>> >> Sure, indentation is what gets the code running on metal :))
>> >>
>> >> Not ranting here, just my abs dying from the pain as I laugh :))
>> >
>> > --
>> > 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 new members are moderated - please be patient with
>> your first post.
>> > To unsubscribe from this group, send email to
>> > clojure+unsubscr...@googlegroups.com
>> > For more options, visit this group at
>> > http://groups.google.com/group/clojure?hl=en
>> > ---
>> > You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> > To unsubscribe from this group and stop recei

Re: [:ann :book] ClojureScript Unraveled

[Bozhidar Batsov]

Sounds like a plan to me. :-)

On 21 July 2015 at 18:16, Alejandro Gómez  wrote:

>  Thanks to everybody for the kind words and suggestions!
>
> A few comments to Bozhidar's suggestions below:
>
> On Mon, Jul 20, 2015, at 07:07, Bozhidar Batsov wrote:
>
> That's a really exciting project, as a lot of people are looking to get
> started with ClojureScript and are finding it kind of hard because of the
> lack of such resources.
>
> My advise would be to put a bit heavier focus on the differences between
> Clojure & ClojureScript and add some section about setting up various
> editors/IDEs.
>
>
> I think the differences from Clojure could be an appendix although it's
> well-documented in the ClojureScript wiki, we'll make sure to mention the
> bigger ones and link to the wiki page (
> https://github.com/clojure/clojurescript/wiki/Differences-from-Clojure).
>
> About the editor/IDE part I agree it'd be nice although is difficult for
> us to write about non-Emacs editors since is what we both use; in my case
> with inferior-clojure mode. It'd be great if Cursive, Light Table, vim & co
> users contribute an appendix about their setup.
>
>
> A chapter like "ClojureScript for Clojure devs" would be great IMO.
>
>
> On 20 July 2015 at 00:51, Alejandro Gómez  wrote:
>
>
> We just released the second revision which includes a lot of corrections,
> an Acknowledgments section and an almost finished chapter about CSP &
> core.async which covers all its API and introduces the CSP concepts.
>
>
>
> - Leanpub: https://leanpub.com/clojurescript-unraveled
> - GitHub repository: https://github.com/funcool/clojurescript-unraveled
> - HTML version: http://funcool.github.io/clojurescript-unraveled/
>
>
>
> On Sun, Jul 19, 2015, at 14:51, Nando Breiter wrote:
>
> I'm a Clojure beginner and wanted to compliment the authors on a very
> clear yet concise text. Thank you.
>
>
>
> Thanks a lot, any feedback will be greatly appreciated since one of the
> goals of the project is to make ClojureScript accesible to newcomers.
>
>
>
>
>
> Aria Media Sagl
> Via Rompada 40
> 6987 Caslano
> Switzerland
>
> +41 (0)91 600 9601
> +41 (0)76 303 4477 cell
> skype: ariamedia
>
> On Fri, Jul 17, 2015 at 7:30 PM, Alejandro Gómez 
> wrote:
>
> Hello everybody,
>
> I'm happy to announce that Andrey Antoukh (@niwinz) and I published the
> book about ClojureScript
> that we have been writing lately on Leanpub. It's not still 100%
> complete but the sections about
> the language and compiler are almost done. We'd greatly appreciate any
> feedback, errata or suggestions
> for the book.
>
> It is an open source book licensed under a Creative Commons BY-SA
> license and will forever remain
> free and open to community participation. Publishing it on Leanpub is a
> convenient way for readers
> to be notified whenever a new release comes out and not to go through
> the process of generating the
> book themselves. If you feel like it and can afford it you can make a
> donation and buy us a beer too!
>
> - Leanpub: https://leanpub.com/clojurescript-unraveled
> - GitHub repository: https://github.com/funcool/clojurescript-unraveled
> - HTML version: http://funcool.github.io/clojurescript-unraveled/
>
> Yours,
>
> Alejandro
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
&g

Re: Tool authors: ClojureScript support in tools.namespace?

[Bozhidar Batsov]

Stuart mentioned that equivalent tools already exist for cljs, but I'm not
sure what he refers to. CIDER makes use of `c.t.n.repl/refresh` (its
lower-level blocks to be precise) and it'd be great if we could provide the
same functionality for cljs.

On 25 July 2015 at 17:37, Dylan Butman  wrote:

> I use .repl constantly for namespace reloading. Clojurescript support
> would be a fantastic improvement for reloading cljs component systems.
>
>
> On Friday, July 24, 2015 at 5:14:04 PM UTC-4, Stuart Sierra wrote:
>>
>> Hello to anyone and everyone writing tools for working with Clojure and
>> ClojureScript source files …
>>
>> I've been looking into adding better support for ClojureScript in
>> tools.namespace.
>>
>> It's not a trivial problem. Lots of places in tools.namespace assume
>> there is only one kind of source file. For Clojure 1.7 it got updated to
>> include .cljc files as well, but it's still hard-coded. I've collected some
>> of my notes in TNS-35: http://dev.clojure.org/jira/browse/TNS-35
>>
>> My question to you: if you maintain a tool or library which uses
>> tools.namespace:
>>
>>1. Do you need/want ClojureScript support?
>>
>>2. What namespaces (repl, find, dir, file, parse) do you call in
>> tools.namespace?
>>
>>3. How would you like to distinguish between "get me Clojure sources"
>> and "get me ClojureScript sources"?
>>
>> Note: I am **not** proposing a full port of tools.namespace to
>> ClojureScript. Something like c.t.n.repl/refresh is too tightly coupled
>> to JVM Clojure, and equivalent tools already exist for ClojureScript.
>>
>> This is just about using tools.namespace to parse and analyze the
>> dependencies of ClojureScript source files, statically, the same way it now
>> does for Clojure source files.
>>
>> Thanks,
>> –S
>>
>  --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Tool authors: ClojureScript support in tools.namespace?

[Bozhidar Batsov]

Sounds like a plan to me. :-)

On 28 July 2015 at 20:35, Stuart Sierra  wrote:

> Thanks for the responses everyone.
>
> So far, my general plan is starting to look like this:
>
> c.t.n.*dependency* and c.t.n.*track* are platform agnostic.
>
> c.t.n.*file* and c.t.n.*parse* can be extended to support Clojure &
> ClojureScript by adding an optional argument read-opts passed through to
> tools.reader/read.
>
> c.t.n.*find* can be extended with optional arguments to select a
> "platform," either Clojure or ClojureScript, which will encapsulate both
> valid file extensions and reader options.
>
> Reload/refresh functionality will remain Clojure(JVM) only for now: c.t.n.
> *dir*, c.t.n.*reload*, and c.t.n.*repl*.
>
> More notes and work-in-progress are visible on TNS-35
> 
>
> I'm not saying there will *never* be any ClojureScript support for
> refresh/reload, just that I have no idea how to do it right now and I want
> to deal with the easier problems first.
>
> –S
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ANN: Namespace browser for Emacs users

[Bozhidar Batsov]

Nicely done! As you might know I'm cider's maintainer and I actually had a 
namespace browser on the roadmap. :-) I'd like to invite you to transfer 
the project to the official clojure-emacs github organisation (to increase 
the package's visibility and to make easier for the cider team to help you 
with the maintenance). 

I hope to eventually include cider-browse-ns in the standard cider package.

On Monday, July 28, 2014 5:48:20 AM UTC+3, John Andrews wrote:
>
> Emacs users: I have put together a namespace browser which builds upon the 
> existing functionality of Cider. It is in early stages of development but I 
> find it quite useful.
>
> Check it out! https://github.com/jxa/cider-browse-ns
>  

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: A few String functions we could implement in Clojure?

[Bozhidar Batsov]

I recently raised a similar point regarding `starts-with?` and `ends-with?` 
(link - http://dev.clojure.org/jira/browse/CLJ-1449) and it seems that 
Clojure's team acknowledges that this is valid reasoning.

I think you should open a ticket as well as the case you present is pretty 
much the same. With ClojureScript and cljx it makes much more sense now to 
create
portable interfaces that it used to before (in the era of Java-only 
Clojure).

On Saturday, July 19, 2014 6:56:44 PM UTC+3, Pierre Masci wrote:
>
> Thank you for your insight Andy :-)
>
> Interesting question Bruce.
>
> -- Pierre Masci
>  
>
> On 19 July 2014 16:49, Andy Fingerhut > 
> wrote:
>
>> I would have to defer that question to someone who makes decisions 
>> regarding what goes into Clojure/ClojureScript, and what does not.
>>
>> Of course, anyone else is free to create libraries that try to make 
>> portability between those two platforms easier.  Perhaps someone has 
>> already taken a go at creating such a thing?  I haven't used ClojureScript 
>> myself yet, so haven't looked for anything in that area.
>>
>> Andy
>>
>>
>> On Sat, Jul 19, 2014 at 8:23 AM, Bruce Durling > > wrote:
>>
>>> Andy,
>>>
>>> How much of this reasoning do you think changes when we starting
>>> thinking about being hosted on multiple platforms (I'm thinking
>>> specifically clojure/clojurescript and cljx)?
>>>
>>> cheers,
>>> Bruce
>>>
>>> On Sat, Jul 19, 2014 at 4:17 PM, Andy Fingerhut
>>> > wrote:
>>> > Pierre:
>>> >
>>> > I maintain the cheatsheet, and I put .indexOf and .lastIndexOf on there
>>> > since they are probably the most common thing I saw asked about that 
>>> is in
>>> > the Java API but not the Clojure API, for strings.  There are also 
>>> links to
>>> > whole Java classes and their entire API, e.g. for file I/O, for which 
>>> there
>>> > is no Clojure equivalent, since file I/O is a common need.  Clojure is 
>>> meant
>>> > to be a hosted language, not hiding its host platform, but making it 
>>> easily
>>> > callable.
>>> >
>>> > If there are entire Java classes that meet very common needs that 
>>> aren't
>>> > mentioned on the cheatsheet, I would consider adding links to their
>>> > documentation pages.  I don't want to fill up the cheatsheet with many
>>> > individual Java methods, though.
>>> >
>>> > As for why there are not Clojure equivalents of particular Java API 
>>> methods,
>>> > I think the reasoning might be similar (it has likely been discussed
>>> > publicly, but I don't have a link handy) -- don't create a large 
>>> number of
>>> > Clojure functions that do nothing more than what the equivalent Java 
>>> APIs
>>> > do.
>>> >
>>> > Andy
>>> >
>>> >
>>> > On Sat, Jul 19, 2014 at 3:58 AM, Pierre Masci >> > wrote:
>>> >>
>>> >> Hi all, just nit picking about Clojure's String API.
>>> >>
>>> >> I've been comparing it with Java's, and I noticed that (not 
>>> surprisingly)
>>> >> they are very similar.
>>> >> There are just 2-3 functions that exist in Java but don't have an
>>> >> equivalent in Clojure. I was wondering if they could be worth adding 
>>> to
>>> >> clojure.string :
>>> >>
>>> >> (.indexOf s "c")   and   (.lastIndexOf "c")
>>> >>
>>> >> (.startsWith s "danc")   and   (.endsWith s "ing")
>>> >>
>>> >> (.charAt s 5)
>>> >> same as (get s 5) but expresses a clearer intent. It's less 
>>> general
>>> >> than (get) though as it only applies to Strings, so that might be
>>> >> unnecessary sugar.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> .indexOf and .lastIndexOf are indicated in the Clojure Cheatsheet, 
>>> maybe
>>> >> .startsWith and .endsWith also deserve to be mentioned there?
>>> >>
>>> >> I've been wondering why some functions have been ported, like 
>>> (lower-case)
>>> >> for (.toLowerCase), but not the ones mentioned above.
>>> >>
>>> >> I told you it was nit picking (^c^) Clojure's API is awesome as it is.
>>> >>
>>> >> --
>>> >> You received this message because you are subscribed to the Google
>>> >> Groups "Clojure" group.
>>> >> To post to this group, send email to clo...@googlegroups.com 
>>> 
>>> >> Note that posts from new members are moderated - please be patient 
>>> with
>>> >> your first post.
>>> >> To unsubscribe from this group, send email to
>>> >> clojure+u...@googlegroups.com 
>>> >> For more options, visit this group at
>>> >> http://groups.google.com/group/clojure?hl=en
>>> >> ---
>>> >> You received this message because you are subscribed to the Google 
>>> Groups
>>> >> "Clojure" group.
>>> >> To unsubscribe from this group and stop receiving emails from it, 
>>> send an
>>> >> email to clojure+u...@googlegroups.com .
>>> >> For more options, visit https://groups.google.com/d/optout.
>>> >
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups "Clojure" group.
>>> > To post to this group, send email to clo...@googlegroups.com 
>>> 
>>> > Note that posts from new members are moderated - please be patient 
>>> with your
>>> > first post.
>>> > To unsub

Re: [ANN] Grimoire 0.3.0

[Bozhidar Batsov]

On Saturday, August 2, 2014, Reid McKenzie  wrote:

> For those of you who didn't notice the ten minutes of 500 pages as I
> upgraded, I'm delighted to announce the Grimoire's 3rd release!
>
> This version would not have been possible without Robert Stuttaford, who
> was a huge help in porting Grimoire off of the original Jekyll back end
> to a real Ring server. Thanks also to Andy Fingerhut, thanks to whom
> Grimoire now incorporates the Thalia extended docstrings.
>
> So what's new?
>  - HTML and plain text API! see http://grimoire.arrdem.com/api for
> details.
>  - Extended & unofficial docstrings from Andy.
>  - Pervasive edit links. If it's templated, you can submit edits to it.
>  - Redesigned examples system which allows for even easier contribution.
>  - Changes to symbol munging which may have broken bookmarks.
>
> This release breaks the "cider-grimoire" command for symbols with
> punctuation and probably breaks some favorites as I took the opportunity
> to discard some symbol munging which was really a Jekyll workaround. In
> retrospect I shouldn't have mucked with that for backwards
> compatibility, but live and learn. Andyf's cheat sheet should be updated
> later today and the updated munge function should appear in next week's
> Cider 0.7.0.


Just a quick note. I actually updated cider-grimoire for 0.3 a few hours
before you released it, so everybody using the latest snapshot should be
fine.  I hope that we'll finally get to release CIDER 0.7 on Monday. I've
also implemented support for the text API (but haven't commited yet) which
should make it into the release.

>
> Comments and complaints are welcome here and on the bug tracker over at
> https://github.com/arrdem/grimoire/issues.
>
> Cheers!
> Reid
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com 
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Grimoire 0.3.0

[Bozhidar Batsov]

On August 2, 2014 at 8:52:48, Bozhidar Batsov (bozhi...@batsov.com) wrote:


On Saturday, August 2, 2014, Reid McKenzie  wrote:
For those of you who didn't notice the ten minutes of 500 pages as I
upgraded, I'm delighted to announce the Grimoire's 3rd release!

This version would not have been possible without Robert Stuttaford, who
was a huge help in porting Grimoire off of the original Jekyll back end
to a real Ring server. Thanks also to Andy Fingerhut, thanks to whom
Grimoire now incorporates the Thalia extended docstrings.

So what's new?
 - HTML and plain text API! see http://grimoire.arrdem.com/api for details.
 - Extended & unofficial docstrings from Andy.
 - Pervasive edit links. If it's templated, you can submit edits to it.
 - Redesigned examples system which allows for even easier contribution.
 - Changes to symbol munging which may have broken bookmarks.

This release breaks the "cider-grimoire" command for symbols with
punctuation and probably breaks some favorites as I took the opportunity
to discard some symbol munging which was really a Jekyll workaround. In
retrospect I shouldn't have mucked with that for backwards
compatibility, but live and learn. Andyf's cheat sheet should be updated
later today and the updated munge function should appear in next week's
Cider 0.7.0.

Just a quick note. I actually updated cider-grimoire for 0.3 a few hours before 
you released it, so everybody using the latest snapshot should be fine.  I hope 
that we'll finally get to release CIDER 0.7 on Monday. I've also implemented 
support for the text API (but haven't commited yet) which should make it into 
the release. 
Another update - I’ve pushed the feature upstream. `M-x cider-grimoire` now 
uses the Grimoire text api. The old command is still around under a new name - 
`cider-grimoire-web` (C-c C-d h). It has a few rough edges, but it’s definitely 
better than nothing.



Comments and complaints are welcome here and on the bug tracker over at
https://github.com/arrdem/grimoire/issues.

Cheers!
Reid

--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ANN: Namespace browser for Emacs users

[Bozhidar Batsov]

On August 5, 2014 at 0:29:33, John Andrews (john.m.andr...@gmail.com) wrote:
Hi Bozhidar,

I think adding it to main Cider sounds like a great idea! I'll work up a pull 
request in the next few days.

Thanks,
John
Looking forward to it! :-)




On Fri, Aug 1, 2014 at 6:09 AM, Bozhidar Batsov  
wrote:
Nicely done! As you might know I'm cider's maintainer and I actually had a 
namespace browser on the roadmap. :-) I'd like to invite you to transfer the 
project to the official clojure-emacs github organisation (to increase the 
package's visibility and to make easier for the cider team to help you with the 
maintenance). 

I hope to eventually include cider-browse-ns in the standard cider package.

On Monday, July 28, 2014 5:48:20 AM UTC+3, John Andrews wrote:
Emacs users: I have put together a namespace browser which builds upon the 
existing functionality of Cider. It is in early stages of development but I 
find it quite useful.

Check it out! https://github.com/jxa/cider-browse-ns
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] CIDER 0.7 is out!

[Bozhidar Batsov]

Hi everyone,

CIDER 0.7.0 is finally out! I wrote a short blog post about it, as the release 
is quite massive and important:

http://batsov.com/articles/2014/08/05/cider-0-dot-7/

Enjoy!

-- 
Cheers,
Bozhidar

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: CIDER vs Org Mode: "Symbol's definition is void: nrepl-send-string-sync" (workaround)

[Bozhidar Batsov]

On August 10, 2014 at 11:51:07 PM, Matching Socks (phill.w...@gmail.com) wrote:
Using Org Mode's org-babel-execute-src-block, I ran into "Symbol's definition 
is void: nrepl-send-string-sync" after installing a recent update of the cider 
package from Melpa.
This was recently renamed - have a look at CIDER's changelog. Interestingly we 
have an alias with the old name, so people should be getting warnings, not 
errors. I’ll have at the problem.



cider-eval-sync appears to be an adequate substitute for the function that 
vanished.  The new function is in the cider-client module.  The usage that 
needs adjustment is in ob-clojure.
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: CIDER vs Org Mode: "Symbol's definition is void: nrepl-send-string-sync" (workaround)

[Bozhidar Batsov]

Indeed. I’ve overlooked this particular function; this is corrected upstream 
now.
-- 
Bozhidar

On August 12, 2014 at 11:53:42, Bastien (bastiengue...@gmail.com) wrote:

Bozhidar Batsov  writes:  

> This was recently renamed - have a look at CIDER's changelog.  
> Interestingly we have an alias with the old name, so people should be  
> getting warnings, not errors. I’ll have at the problem.  

I think the attached patch should fix the problem.  


--  
Bastien  

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Gorilla REPL 0.3.3 - inline docs, CIDER compatibility

[Bozhidar Batsov]

vim-fireplace uses cider-nrepl (when available, otherwise it will fallback to 
evaling inlined code) as well, so the Emacs rules should apply for it.
—
Cheers, 
Bozhidar

On September 1, 2014 at 2:12:53 PM, Jony Hudson (jonyepsi...@gmail.com) wrote:

Ohh, and there are some new docs on how to use Gorilla alongside your favourite 
editor/IDE:

http://gorilla-repl.org/editors.html


Jony
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Gorilla REPL 0.3.3 - inline docs, CIDER compatibility

[Bozhidar Batsov]

On September 1, 2014 at 2:11:40 PM, Jony Hudson (jonyepsi...@gmail.com) wrote:
Hi all,

 there's a new version of Gorilla REPL out :-) The headline feature is that the 
autocomplete UI now shows the docs for the function you're typing/lets you 
browse the docs. It's really handy! Autocomplete itself is also much improved, 
courtesy of the compliment library.

This version also adds compatibility with the latest version of CIDER, and a 
number of other smaller fixes and features (see changelog below).

I must give credit here to the CIDER team, who have done a great job of writing 
CIDER's back-end code in a way that it can be re-used by other editors. It must 
have taken some work to do that, and it's a very useful contribution to Clojure 
tooling. Gorilla now uses CIDER's back-end for autocompletion and 
documentation. Hats off to them!
Thanks! :-) You might also find the var-info middleware quite useful - cider 
and fireplace use it for code navigation and enhanced documentation (eldoc and 
a replacement for (doc something) that works for both Clojure(Script) and Java 
symbols).



>From the changelog:

## Version 0.3.3

- Look up symbol in ClojureDocs.
- Inline documentation in auto-complete.
- Much better auto-complete, thanks to compliment and cider-nrepl.
- Autoselects a free port by default.
- Upgrade to CodeMirror 4.5.
- Interoperable with Emacs/CIDER > v.0.7.0 i.e. auto-adds cider-nrepl 
middleware.
- Hopefully fix an odd intermittent dependency bug (thanks to @jococo).
- App routes now a var for easier hacking on the server (thanks to @ticking).
- Write out web-app port to file on startup to enable other tools to 
interoperate.
- Fix version range warning.



Jony
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: {ANN} defun: A beautiful macro to define clojure functions with pattern match.

[Bozhidar Batsov]

Cool idea! I really wish something similar was available out-of-the-box - 
perhaps it makes sense to include such a macro in core.match itself as some 
point?

—
Cheers, 
Bozhidar

On September 14, 2014 at 9:47:21 AM, dennis zhuang (killme2...@gmail.com) wrote:


Hi , i am pleased to introduce defun: a beautiful macro to define clojure 
functions with pattern match.

Some examples:

(defun say-hi
  ([:dennis] "Hi,good morning, dennis.")
  ([:catty] "Hi, catty, what time is it?")
  ([:green] "Hi,green, what a good day!")
  ([other] (str "Say hi to " other)))

(say-hi :dennis)
;;  "Hi,good morning, dennis."
(say-hi :catty)
;;  "Hi, catty, what time is it?"
(say-hi :green)
;;  "Hi,green, what a good day!"
(say-hi "someone")
;;  "Say hi to someone"

Recursive function? It's all right:

(defun count-down
  ([0] (println "Reach zero!"))
  ([n] (println n)
     (recur (dec n
(defun fib
    ([0] 0)
    ([1] 1)
    ([n] (+ (fib (- n 1)) (fib (- n 2)


Guard functions? it's all right:

(defun valid-geopoint?
    ([(_ :guard #(and (> % -180) (< % 180)))
      (_ :guard #(and (> % -90) (< % 90)))] true)
    ([_ _] false))

(valid-geopoint? 30 30)
;; true
(valid-geopoint? -181 30)
;; false

It's really cool,all the magic are from core.match, much more details please 
see 
https://github.com/killme2008/defun


--
庄晓丹
Email:    killme2...@gmail.com xzhu...@avos.com
Site:   http://fnil.net
Twitter:  @killme2008


--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Clojure Videos (with options for Linux users)

[Bozhidar Batsov]

I was thinking the same thing. Lack of paypal support is the only reason I 
haven’t subscribed yet…

Not sure if it’s something supported by pivotshare, though.

—
Cheers, 
Bozhidar

On September 22, 2014 at 5:52:05 PM, Mateusz Fiołka (mateusz.fio...@gmail.com) 
wrote:


Paypal payment option would be nice.


On Friday, September 19, 2014 2:51:46 AM UTC+2, tbc++ wrote:
Just wanted to throw this out there, but I've been making steady progress on my 
Clojure Tutorial Videos (https://tbaldridge.pivotshare.com). We're up to 43 
videos with new episodes added at a rate of about 2-3 a week. 

Some users have expressed a desire for the raw MP4 files for use on Linux, or 
other platforms where flash is not optimal, so I'm also happy to announce that 
the videos are available via Dropbox. There's a link on the site, the price is 
the same, but the process is manual so there is a processing delay of 1-2 days. 

Thanks to everyone who's offered encouragement and feedback. And 
yes...transducer videos will be up *soon*. They're recorded, but you should 
really start by watching the video of Rich's Strange Loop talk, that he'll be 
giving tomorrow. 


--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Monroe 0.1.0 - nrepl client for Emacs

[Bozhidar Batsov]

Btw, you’re using CIDER’s old bencode parser, which was flawed (big requests 
break it due to deep recursive calls). We recently reworked it and the new 
version is much more robust.

—
Cheers, 
Bozhidar

On September 25, 2014 at 4:32:12 PM, Sanel Zukan (san...@gmail.com) wrote:

Thanks for reply with the details, Bastien :)

> As someone new to CIDER (probably only use 10% of its features), what's the 
>difference between this and CIDER?

I think you already answered it :) I find Cider amazing project, but is a bit 
biggish for my taste, especially if you would like to get the extension and 
start working on Clojure code, instead of setting up the details. Also, I 
prefer keeping REPL and all REPL related stuff (erorrs and exceptions) _inside_ 
REPL buffer and window, just like many Emacs modes works.

Now, a little bit internals: Monroe REPL is using comint-mode, which means that 
many comint keys and variables should work out of the box. In Emacs, 
comint-mode is used by default for interaction with external programs like 
shell, ielm, inferior-[lisp, scheme, python] and many of them are sharing 
similar shortcuts.

> i.e. why would I want to use this over CIDER? (could be good to put in the 
> README as well)

I think README summarize the goals behind the project. If you find it 
confusing, I'll try to clarify the things a little bit.

Best,
Sanel

On Thursday, September 25, 2014 6:41:52 AM UTC+2, Bastien Guerry wrote:
John Louis Del Rosario  writes:

> Looks neat. As someone new to CIDER (probably only use 10% of its
> features), what's the difference between this and CIDER? i.e. why
> would I want to use this over CIDER? (could be good to put in the
> README as well)

Copying what's on the reddit page:

http://www.reddit.com/r/Clojure/comments/2hde6w/monroe_new_nrepl_client_for_emacs/

"Some features:

- lightweight
   
- focused only on nrepl protocol so you can easily combine it with
  favorite libraries (e.g. company-mode)
   
- single buffer for interaction, which behaves like inferior
  modes. Errors and results will be shown in that buffer, instead
  poping out new buffers.
   
- works on older Emacs versions
   
- history in repl that actually works"

--
 Bastien
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Monroe 0.1.0 - nrepl client for Emacs

[Bozhidar Batsov]

On October 3, 2014 at 3:06:08 PM, Daniel Szmulewicz 
(daniel.szmulew...@gmail.com) wrote:
Hi Sanel and thanks for Monroe. 

I think the use case is clear: lightweight alternative to Cider. 
So the question is what is the use case pertaining to nrepl.el, which is also 
lightweight.
This question is a bit confusing as nrepl.el is cider’s old name. You can't 
really compare something with itself, but you can compare an old version of a 
project with its current version.



On Wednesday, September 24, 2014 7:50:52 PM UTC+3, Sanel Zukan wrote:
Hi everyone,

Here is initial release for Monroe, a new Clojure nREPL client for Emacs. The 
main idea behind Monroe is to be simple, easy to install (just put it in your 
load-path) and to work like inferior modes (inferior-lisp or inferior-scheme), 
providing common keybindings in REPL, including color and history support. You 
will also need clojure-mode.el for code syntax highlighting, but this is 
optional.

This initial release is ready for consumption (I'm using it on a bit larger 
project) and feel free to drop me a line if you find some issues.

Again, the url is https://github.com/sanel/monroe

Best,
Sanel
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Monroe 0.1.0 - nrepl client for Emacs

[Bozhidar Batsov]

Yeah, they should definitely remove nrepl.el support from ob-clojure.el.

— 
Cheers,
Bozhidar

On October 3, 2014 at 15:40:31, Daniel Szmulewicz (daniel.szmulew...@gmail.com) 
wrote:

You're right. 
I got confused because in ob-clojure.el, both cider and nrepl.el are considered 
back-ends, so I thought they were separate things. So in fact, nrepl.el is just 
an old incarnation of Cider? Ob-clojure.el needs a fixing, I believe.


Oops, I meant nrepl.el: 
https://github.com/technomancy/nrepl.el/blob/master/nrepl.el

On Friday, October 3, 2014 3:34:26 PM UTC+3, Bozhidar Batsov wrote:
On October 3, 2014 at 3:06:08 PM, Daniel Szmulewicz (daniel.s...@gmail.com) 
wrote:
Hi Sanel and thanks for Monroe. 

I think the use case is clear: lightweight alternative to Cider. 
So the question is what is the use case pertaining to nrepl.el, which is also 
lightweight.
This question is a bit confusing as nrepl.el is cider’s old name. You can't 
really compare something with itself, but you can compare an old version of a 
project with its current version.



On Wednesday, September 24, 2014 7:50:52 PM UTC+3, Sanel Zukan wrote:
Hi everyone,

Here is initial release for Monroe, a new Clojure nREPL client for Emacs. The 
main idea behind Monroe is to be simple, easy to install (just put it in your 
load-path) and to work like inferior modes (inferior-lisp or inferior-scheme), 
providing common keybindings in REPL, including color and history support. You 
will also need clojure-mode.el for code syntax highlighting, but this is 
optional.

This initial release is ready for consumption (I'm using it on a bit larger 
project) and feel free to drop me a line if you find some issues.

Again, the url is https://github.com/sanel/monroe

Best,
Sanel
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: book for a beginner with some exercises

[Bozhidar Batsov]

http://programmingpraxis.com/ is another source of great programming exercises 
(with solutions available in many languages).

— 
Cheers,
Bozhidar

On October 18, 2014 at 23:57:00, Eric Normand (ericwnorm...@gmail.com) wrote:

Hi there,

If you're looking for books, I don't know of any. But my Intro to Clojure 
videos have lots of exercises and start from the beginning.

http://www.purelyfunctional.tv/intro-to-clojure

In terms of exercises, I cut my Clojure teeth on Project Euler. 
https://projecteuler.net/ Once you solve a problem, you'll get access to lots 
of solutions in many languages. Very good problems.

Thanks
Eric

On Tuesday, October 14, 2014 6:57:50 AM UTC-5, Roelof Wobben wrote:
Hello,

Is there a book for a beginner in Clojure where I can learn things and practice 
the things I learned with some exercises ?

Roelof

--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Print broken in Cider 0.7.0 - Ring - Compojure

[Bozhidar Batsov]

I recall that a similar problem was caused by a buggy nREPL version. 
See https://github.com/clojure-emacs/cider/issues/785

—
Cheers, 
Bozhidar

On October 29, 2014 at 2:41:02 PM, Steve Shogren (steve.a.shog...@gmail.com) 
wrote:

I cannot seem to see the results of "println", "print", or 
"clojure.tools.trace/trace" when running my site, per my setup here: 
http://stackoverflow.com/questions/22365741/missing-out-in-clojure-with-lein-and-ring?lq=1

The one comment suggested trying (.println
System/out msg) which prints as I would expect, but the others still do not. 
Any ideas how I could fix trace, print, and println?

Thanks!
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Print broken in Cider 0.7.0 - Ring - Compojure

[Bozhidar Batsov]

I’d suggest filing the a ticket with output from *nrepl-messages* so we can 
have an idea what’s going on.
You can also try the 0.8-snapshot.

—
Cheers, 
Bozhidar

On October 29, 2014 at 5:43:56 PM, Steve Shogren (steve.a.shog...@gmail.com) 
wrote:

Supposedly that was fixed in nrepl 0.2.6, which is the version I am using. 
Still nothing.

On Wednesday, October 29, 2014 10:15:34 AM UTC-4, Bozhidar Batsov wrote:
I recall that a similar problem was caused by a buggy nREPL version. 
See https://github.com/clojure-emacs/cider/issues/785

—
Cheers, 
Bozhidar

On October 29, 2014 at 2:41:02 PM, Steve Shogren (steve.a...@gmail.com) wrote:

I cannot seem to see the results of "println", "print", or 
"clojure.tools.trace/trace" when running my site, per my setup here: 
http://stackoverflow.com/questions/22365741/missing-out-in-clojure-with-lein-and-ring?lq=1

The one comment suggested trying (.println
System/out msg) which prints as I would expect, but the others still do not. 
Any ideas how I could fix trace, print, and println?

Thanks!
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Introducing inf-clojure - a better basic Clojure REPL for Emacs

[Bozhidar Batsov]

At Clojure/conj I had the chance to shake Rich Hickey’s hand and exchange a few 
words with him. When I asked him whether he currently uses CIDER or Cursive for 
Clojure development he replied that he preferred a simpler solution - 
clojure-mode & inferior-lisp-mode. I was a bit surprised because clojure-mode’s 
integration with inferior-lisp-mode sucks (big time). It has always been 
extremely limited and was never really improved/extended. It has no Clojure 
specific features and no code completion. I felt that Rich and all the people 
using inferior-lisp-mode deserved something better, so I quickly put together 
inf-clojure.

inf-clojure provides some Clojure specific features like showing a var’s doc or 
source, derives some core functionality from clojure-mode and even features 
basic code-completion (and company-mode support). That’s not much admittedly, 
but it’s a good start. Extending inf-clojure is super easy and I expect that 
we’ll add a bit more features to it along the way (e.g. macroexpansion).

inf-clojure is available in MELPA and will eventually replace completely 
inferior-lisp-mode when clojure-mode 4.0 is released.

Keep in mind that inf-clojure is nothing like CIDER and will never be. CIDER 
will always be the powertool for Clojure programming in Emacs. I do understand, 
however, that some people are overwhelmed by CIDER and some people simply don’t 
need anything sophisticated. I hope they’ll enjoy inf-clojure!



—
Cheers, 
Bozhidar

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Introducing inf-clojure - a better basic Clojure REPL for Emacs

[Bozhidar Batsov]

That’s odd. `clojure-source-modes` is a defcustom with value '(clojure-mode) by 
default. Tried this locally and it seems to work.

— 
Cheers,
Bozhidar

On December 4, 2014 at 23:24:04, Bastien (bastiengue...@gmail.com) wrote:

Hi Bozhidar,  

Bozhidar Batsov  writes:  

> inf-clojure is available in MELPA and will eventually replace  
> completely inferior-lisp-mode when clojure-mode 4.0 is released.  

Good idea! I just tried to install it through MELPA and got  
this error:  

Debugger entered--Lisp error: (void-variable clojure-source-modes)  
(let ((--dolist-tail-- clojure-source-modes) mode) (while --dolist-tail-- (setq 
mode (car --dolist-tail--)) (add-hook (intern (format "%s-hook" mode)) (quote 
inf-clojure-minor-mode)) (setq --dolist-tail-- (cdr --dolist-tail--  
eval-buffer(# nil 
"/home/guerry/.emacs.d/elpa/inf-clojure-20141204.820/inf-clojure-autoloads.el" 
nil t) ; Reading at buffer position 1128  
load-with-code-conversion("/home/guerry/.emacs.d/elpa/inf-clojure-20141204.820/inf-clojure-autoloads.el"
 "/home/guerry/.emacs.d/elpa/inf-clojure-20141204.820/inf-clojure-autoloads.el" 
nil t)  
load("/home/guerry/.emacs.d/elpa/inf-clojure-20141204.820/inf-clojure-autoloads"
 nil t)  
#[0 "\302\303\304\305\300\"\301\"\306\307#\207" [inf-clojure 
"/home/guerry/.emacs.d/elpa/inf-clojure-20141204.820" load expand-file-name 
format "%s-autoloads" nil t] 5 "\n\n(fn)"]()  
funcall(#[0 "\302\303\304\305\300\"\301\"\306\307#\207" [inf-clojure 
"/home/guerry/.emacs.d/elpa/inf-clojure-20141204.820" load expand-file-name 
format "%s-autoloads" nil t] 5 "\n\n(fn)"])  
package-activate-1([cl-struct-package-desc inf-clojure (20141204 820) "an 
inferior-clojure mode" ((emacs (24 1)) (clojure-mode (3 0))) nil nil 
"/home/guerry/.emacs.d/elpa/inf-clojure-20141204.820" ((:keywords "processes" 
"clojure") (:url . "http://github.com/clojure-emacs/inf-clojure";)) nil])  
package--compile([cl-struct-package-desc inf-clojure (20141204 820) "an 
inferior-clojure mode" ((emacs (24 1)) (clojure-mode (3 0))) nil nil 
"/home/guerry/.emacs.d/elpa/inf-clojure-20141204.820" ((:keywords "processes" 
"clojure") (:url . "http://github.com/clojure-emacs/inf-clojure";)) nil])  
package-unpack([cl-struct-package-desc inf-clojure (20141204 820) "an 
inferior-clojure mode" ((emacs (24 1)) (clojure-mode (3 0))) single "melpa" nil 
((:url . "http://github.com/clojure-emacs/inf-clojure";) (:keywords "processes" 
"clojure")) nil])  
package-install-from-archive([cl-struct-package-desc inf-clojure (20141204 820) 
"an inferior-clojure mode" ((emacs (24 1)) (clojure-mode (3 0))) single "melpa" 
nil ((:url . "http://github.com/clojure-emacs/inf-clojure";) (:keywords 
"processes" "clojure")) nil])  
mapc(package-install-from-archive ([cl-struct-package-desc clojure-mode 
(20141204 854) "Major mode for Clojure code" ((emacs (24 1))) single "melpa" 
nil ((:url . "http://github.com/clojure-emacs/clojure-mode";) (:keywords 
"languages" "clojure" "clojurescript" "lisp")) nil] [cl-struct-package-desc 
inf-clojure (20141204 820) "an inferior-clojure mode" ((emacs (24 1)) 
(clojure-mode (3 0))) single "melpa" nil ((:url . 
"http://github.com/clojure-emacs/inf-clojure";) (:keywords "processes" 
"clojure")) nil]))  
package-download-transaction(([cl-struct-package-desc clojure-mode (20141204 
854) "Major mode for Clojure code" ((emacs (24 1))) single "melpa" nil ((:url . 
"http://github.com/clojure-emacs/clojure-mode";) (:keywords "languages" 
"clojure" "clojurescript" "lisp")) nil] [cl-struct-package-desc inf-clojure 
(20141204 820) "an inferior-clojure mode" ((emacs (24 1)) (clojure-mode (3 0))) 
single "melpa" nil ((:url . "http://github.com/clojure-emacs/inf-clojure";) 
(:keywords "processes" "clojure")) nil]))  
package-install([cl-struct-package-desc inf-clojure (20141204 820) "an 
inferior-clojure mode" ((emacs (24 1)) (clojure-mode (3 0))) single "melpa" nil 
((:url . "http://github.com/clojure-emacs/inf-clojure";) (:keywords "processes" 
"clojure")) nil])  
package-install-button-action(#)  
button-activate(# nil)  
push-button(76)  
call-interactively(push-button nil nil)  
command-execute(push-button)  

--  
Bastien  

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Introducing inf-clojure - a better basic Clojure REPL for Emacs

[Bozhidar Batsov]

It doesn’t use nREPL at all making it the simplest solution possible (meaning 
you can’t use it to connect to remote processes).
The value of monroe is pretty questionable IMO as you can use CIDER as a 
replacement for monroe anyways (basic CIDER features work even without the 
cider-nrepl middleware). 

— 
Cheers,
Bozhidar

On December 5, 2014 at 03:43:03, John Louis Del Rosario (joh...@gmail.com) 
wrote:

How does this differ to monroe https://github.com/sanel/monroe?

On Friday, December 5, 2014 1:39:32 AM UTC+8, Bozhidar Batsov wrote:
At Clojure/conj I had the chance to shake Rich Hickey’s hand and exchange a few 
words with him. When I asked him whether he currently uses CIDER or Cursive for 
Clojure development he replied that he preferred a simpler solution - 
clojure-mode & inferior-lisp-mode. I was a bit surprised because clojure-mode’s 
integration with inferior-lisp-mode sucks (big time). It has always been 
extremely limited and was never really improved/extended. It has no Clojure 
specific features and no code completion. I felt that Rich and all the people 
using inferior-lisp-mode deserved something better, so I quickly put together 
inf-clojure.

inf-clojure provides some Clojure specific features like showing a var’s doc or 
source, derives some core functionality from clojure-mode and even features 
basic code-completion (and company-mode support). That’s not much admittedly, 
but it’s a good start. Extending inf-clojure is super easy and I expect that 
we’ll add a bit more features to it along the way (e.g. macroexpansion).

inf-clojure is available in MELPA and will eventually replace completely 
inferior-lisp-mode when clojure-mode 4.0 is released.

Keep in mind that inf-clojure is nothing like CIDER and will never be. CIDER 
will always be the powertool for Clojure programming in Emacs. I do understand, 
however, that some people are overwhelmed by CIDER and some people simply don’t 
need anything sophisticated. I hope they’ll enjoy inf-clojure!



—
Cheers, 
Bozhidar
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: For review: Clojure Namespace Isolation

[Bozhidar Batsov]

I think you should post this to clojure-...@googlegroups.com

— 
Cheers,
Bozhidar

On December 7, 2014 at 07:32:38, Ralph Ritoch (rrit...@gmail.com) wrote:

Hello,

   I have created a way to create namespace isolation within clojure. The code 
is available on github @ https://github.com/rritoch/clojure .  What this new 
code does is it replaces the clojure.lang.Namespace/namespaces static property 
with a clojure.lang.NamespaceContainer object that is a version which utilizes 
thread local memory and facilitates creating separate namespace environments 
within a single Runtime.

To create and enter a new environment.

(clojure.lang.NamespaceContainer/enter)

This returns a pointer which can later be used to re-enter the namespace as the 
enter method also takes a single argument of that pointer.

To leave the isolation environment ...

(clojure.lang.NamespaceContainer/exit)

When used with OSGi this should make it possible to maintain a single Runtime 
per clojure version running on a system.

To ensure maximum stability, the current namespace and all of it's dependent 
namespaces are copied into the newly created container. Once inside a new 
container, changes can be made without any risk of namespace conflicts with 
other parts of the system.

I would like to submit these features for addition to Clojure.

Best Regards,
  Ralph Ritoch
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

CIDER 0.8.2 released!

[Bozhidar Batsov]

Ladies and gentlemen, I’m happy to inform you that CIDER 0.8.2 is out! It’s a 
bugfix-only release (which means you totally want to use it). Have a look at 
the release notes (https://github.com/clojure-emacs/cider/releases/tag/v0.8.2) 
for all the gory details.

This will be the final release in the 0.8.x series (unless some terrible 
regression doesn’t pop up). There are no concrete plans for 0.9 yet, but I hope 
it will introduce some (or ideally all) of the following:

* better cljs support

* comint-based REPL buffers

* boot support

* better handling of multiple nREPL connections

* and whatever else we manage to fit in :-)

Please, report bugs and submit suggestions for improvements here 
https://github.com/clojure-emacs/cider/issues. If you like clojure-mode, CIDER 
and inf-clojure you can support their development via Gratipay 
https://gratipay.com/bbatsov/

P.S. In related news - squiggly-clojure 
(https://github.com/clojure-emacs/squiggly-clojure), a flycheck extension for 
CIDER is now an official clojure-emacs project.

-- 

Cheers,
Bozhidar

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Clojure Style Guide

[Bozhidar Batsov]

The only catch is that you should do this only for “relatively unique” names, 
as clojure-mode is not namespace aware. Otherwise you might get
funky indentation in odd places.

—
Cheers, 
Bozhidar

On December 21, 2014 at 3:23:17 AM, Reid McKenzie (rmckenzi...@gmail.com) wrote:

Protip: you already can. From my .emacs:  

(define-clojure-indent  
(defroutes 'defun)  
(GET 2)  
(POST 2)  
(PUT 2)  
(DELETE 2)  
(HEAD 2)  
(ANY 2)  
(context 2)  
(for-all 1)  
(such-that 1)  
(let-routes 1)  
(run-db 2)  
(defspec 'defun))  

Reid  

On 12/20/14 16:28, John Jacobsen wrote:  
> Great to see this discussion on the mailing list, rather than just  
> comments to PRs on GitHub. And a big thanks to Bozhidar for shepherding  
> the current style guide.  
>  
> I came to Clojure from Python which has a strict standard (PEP-8) and a  
> linting tool which enforces a standard -- it's been my experience that  
> this provides a net benefit to code quality (and not just in terms of  
> aesthetics). While I also don't agree with everything currently in the  
> style guide, it does some good in our shop by providing a default to  
> refer to which eliminates some wasted discussion time.  
>  
> So far the PR process on the style guide repo seems to have worked, more  
> or less -- those in the community who care about these things can weigh  
> in, and there at least can be a discussion before the PR is merged.  
> Perhaps more process or formality will become appropriate later as the  
> community grows.  
>  
> Regarding indentation metadata or editor customizations: I've seen  
> Cursive/IntelliJ accept directives for indenting specific forms  
> (usually, macros) and I'd like to be able to do that with clojure-mode  
> in Emacs.  
>  
> John  
>  
> --  
> 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 new members are moderated - please be patient with  
> your first post.  
> To unsubscribe from this group, send email to  
> clojure+unsubscr...@googlegroups.com  
> For more options, visit this group at  
> http://groups.google.com/group/clojure?hl=en  
> ---  
> You received this message because you are subscribed to the Google  
> Groups "Clojure" group.  
> To unsubscribe from this group and stop receiving emails from it, send  
> an email to clojure+unsubscr...@googlegroups.com  
> .  
> For more options, visit https://groups.google.com/d/optout.  

--  
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 new members are moderated - please be patient with your 
first post.  
To unsubscribe from this group, send email to  
clojure+unsubscr...@googlegroups.com  
For more options, visit this group at  
http://groups.google.com/group/clojure?hl=en  
---  
You received this message because you are subscribed to the Google Groups 
"Clojure" group.  
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.  
For more options, visit https://groups.google.com/d/optout.  

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: CIDER 0.8.2 released!

[Bozhidar Batsov]

On December 21, 2014 at 1:29:04 PM, László Török (ltoro...@gmail.com) wrote:
This is fantastic! Congrats and kudos to all the contributors. 

One question: will the 0.8.2 release make it to MELPA-stable?
Sure. No idea how often the MELPA-stable packages get rebuilt, but I expect 
0.8.2 to land there in the next few hours.



Thanks! 

L

2014-12-21 11:54 GMT+01:00 Bozhidar Batsov :
Ladies and gentlemen, I’m happy to inform you that CIDER 0.8.2 is out! It’s a 
bugfix-only release (which means you totally want to use it). Have a look at 
the release notes (https://github.com/clojure-emacs/cider/releases/tag/v0.8.2) 
for all the gory details.

This will be the final release in the 0.8.x series (unless some terrible 
regression doesn’t pop up). There are no concrete plans for 0.9 yet, but I hope 
it will introduce some (or ideally all) of the following:

* better cljs support

* comint-based REPL buffers

* boot support

* better handling of multiple nREPL connections

* and whatever else we manage to fit in :-)

Please, report bugs and submit suggestions for improvements here 
https://github.com/clojure-emacs/cider/issues. If you like clojure-mode, CIDER 
and inf-clojure you can support their development via Gratipay 
https://gratipay.com/bbatsov/

P.S. In related news - squiggly-clojure 
(https://github.com/clojure-emacs/squiggly-clojure), a flycheck extension for 
CIDER is now an official clojure-emacs project.

-- 

Cheers,
Bozhidar
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
László Török


--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Clojure Style Guide

[Bozhidar Batsov]

On December 20, 2014 at 11:14:14 AM, Colin Fleming 
(colin.mailingl...@gmail.com) wrote:
Hi everyone,

There's been a bit of discussion recently on a couple of clojure-mode tickets 
that I thought were worth discussing here. The tickets are #265 and #266, and 
they later led to PR #96 on Bozhidar Batsov's Clojure Style Guide. The part of 
the discussion I wanted to raise starts here, where there's some discussion 
around the nature of the style guide itself.

Bozhidar clearly sees himself as the steward of a community style guide, 
something he's done to great success with the Ruby style guide. However it 
seems that there is a significant part of the community that didn't see it that 
way, and had seen it more as his personal style guide that he happened to put 
out there. I'm interested in starting a discussion around this because I do 
think it's valuable to have some degree of community consensus around these 
issues, specifically so that tools can have consistent defaults.
I do not agree with everything on the guide on a personal level, which is a 
clear indication this is not a reflection of my personal preferences. On the 
other hand every such document needs an editor (or a few editors), otherwise 
chaos is bound the ensue. When I work on open-source projects I follow the 
style guide pretty closely, but on personal projects I do whatever pleases me. 
Even if people/teams/etc don’t agree with everything in a style guide, there’s 
lots of value in maintaining a consistent code base (which is the same as 
having a style guide). Forking the existing community guide is one of the 
easiest ways to quickly set up an internal project/company style guide. 

I believe that having at least some level of community-wide adopted standards 
simplifies the lives of everyone involved, because we spent less time dwelling 
on details (e.g. code layout) and more time thinking about solving the problems 
at hand. I actually want to talk about the value of style of at either 
Clojure/West or EuroClojure. We’ll see if this will actually happen.



That said, one of the defining features of lisps in general is that they permit 
essentially unlimited flexibility, and in my experience programmers in general 
really don't like being told what to do, especially around indentation. So, I'd 
like to ask the obvious initial question - do we as a community think that 
there is value in having a style guide like this? If so, to Marshall's point on 
the list, do we think it should try to mandate what people should be doing, or 
should it describe what they actually currently do in real code, even if that's 
the result of historical accidents?
I feel that we should promote the “best” (meaning most robust/sensible 
practices over those that are historical accidents). What qualifies as a 
historical accident, however, is rarely clear-cut. I’d argue that the `cond` 
1-space indentation was one such case, but few other examples come to mind.

While I realise that people always have personal preferences regarding code 
style, we should keep in mind that we rarely work by ourselves on a particular 
project and someone will always have to put their personal preferences aside. 
When we started the Ruby style guide there was little consensus regarding 
anything in the Ruby world. Pretty much every project I encountered had a style 
of its own, which introduced a certain cognitive burden on the readers of its 
source code. 4 years later there’s widespread consensus on a lot of basic stuff 
and that’s clearly visible. Sure, there are many aspects on which there will 
never be a consensus (often for a good reason), but having some baseline 
definitely beats having none at all. After all - making choices is pretty hard, 
so the less we have to make the better. 



For what it's worth, from my point of view I definitely think that a guide like 
this is useful, and I've referred to Bozhidar's guide myself from time to time 
when trying to decide what to do for a particular feature in Cursive. However I 
do think that it needs more flexibility than it currently has - there are some 
things marked in there as "bad" that I'd like to see downgraded to "prefer the 
other way unless you have a good reason", which of course I always feel like I 
have. In particular, some of the reasoning behind the linked changes above I 
think needs to be more flexible - there are good use cases for customising 
indentation for some functions, for example.
The use of the words “good” and “bad” is somewhat unfortunate I guess; lately 
we’ve also been using “acceptable” and “preferable” as well. The guide ends 
with something like “use common sense”. The rules are mostly prescriptive - if 
you know Clojure well enough and you feel you have to violate some of them you 
should probably do so.



Of course, if we decide that we do want a guide like this then we can spend 
many happy years arguing about what should go in it, but first things first :-)

Cheers,
Colin
--
You r

Re: Clojure Style Guide

[Bozhidar Batsov]

Yeah, shared (or at least as shared as possible) defaults would be awesome. I 
feel that the style guide might provide us with
some insight about what those shared defaults should be.

—
Cheers, 
Bozhidar

On December 20, 2014 at 11:51:33 AM, Laurent PETIT (laurent.pe...@gmail.com) 
wrote:

I agree that if all tools could agree on sale out of the box defaults, this 
would be very valuable to users and clojure in general. 

Maybe a less ambitious goal than getting the whole community agree on standards 
could be tool authors to agree on shared defaults. Which of course doesn't 
prevent the tools to offer additional options, but activating those would 
require users to explicitly customize the tools settings. 

Le samedi 20 décembre 2014, Lars Andersen  a écrit :
My view on this is very much along the line of discussions about whitespace.  
While I have opinions about these matters, for the most part I don't want to 
think about it--I have more pressing concerns.  What's important to me is 
consistency within a code base.  Just like with whitespace, I don't want to 
introduce spurious changes into all my diffs when working with other people.  I 
also don't want to customize 50 editor variables to get sane defaults which I 
have to tweak for various environments (work, home, contributing to open source 
projects).

Supporting different styles is a laudable goal, but I hope we can agree that 
the defaults should be similar in all editors to reduce friction when working 
with others.  Using a style guide maintained by the community for those 
defaults make a lot of sense to me.
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
Laurent Petit

--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Clojure Style Guide

[Bozhidar Batsov]

On December 20, 2014 at 4:30:41 PM, Timothy Baldridge (tbaldri...@gmail.com) 
wrote:
I recently browsed parts of that guide and was surprised how many bits I 
disagreed with. Especially around the "one space in these rare cases" bits. Not 
that that is a bad thing it's just my personal opinion that everything should 
always use two space indentation.
Can you elaborate on “one space in these rare cases”. I can think of just one 
case (arguments following function/macro name on the next line) of such 
indentation and this is something rooted in Lisp’s DNA. :-)



And on a client project recently, it was decided (when I wasn't around) that 
the arguments to a function should always be on a newline:

(defn foo
  [x]
  (+ x x))

Instead of:

(defn foo [x]
  (+ x x))

I disagree with this idea also, but whatever, it's just style. It's not like I 
suddenly can't read Clojure code since it's in the wrong style. 

With so many different views, I think it's unwise to lock any editor into any 
style. Instead give users options, and update the Clojure Style Guide with the 
following (paraphrased) quote from Pirates of the Caribbean: "this Code of 
Styling is more what you'd call "guidelines" than actual rules."
This is the final rule 
https://github.com/bbatsov/clojure-style-guide#common-sense :-)

That said, we should probably mention something similar in the overture. PEP-8 
has something similar 
https://www.python.org/dev/peps/pep-0008/#a-foolish-consistency-is-the-hobgoblin-of-little-minds



Timothy

On Sat, Dec 20, 2014 at 6:11 AM, Fluid Dynamics  wrote:
A way to hint indentation to the tooling would be nice.

Perhaps a metadata on vars such as {:body-indent #{then-clause else-clause}} 
that could tell tools to indent an "if" this way:

(if condition
  then-clause
  else-clause)

instead of this way:

(if condition
    then-clause
    else-clause)

rather than the current ad-hoc special-casing that seems to be used at present. 
(Ad hoc special-casing would still be needed for special forms, including "if", 
but this could be used with macros and perhaps with functions if someone wanted 
that.)

(Formal specification for that suggestion: the metadata key :body-indent should 
have a value that is a set of symbols, which are some subset of the symbols 
appearing in arglists of the bound macro/function. Editors and pretty-printers 
and other tools would take this as a hint to indent the corresponding 
parameters only two spaces, if on lines of their own, rather than to align with 
parameters inline with the operator on the form's first line.)

--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
“One of the main causes of the fall of the Roman Empire was that–lacking 
zero–they had no way to indicate successful termination of their C programs.”
(Robert Firth)
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Clojure Style Guide

[Bozhidar Batsov]

You can use `.dir-locals.el` to alter the clojure-mode indentation settings on 
a per-project basis.

—
Cheers, 
Bozhidar

On December 20, 2014 at 8:47:10 PM, Andy L (core.as...@gmail.com) wrote:

Hi,

I realized recently that cohesive pretty formatting LISP programs is a very 
difficult problem to solve in the first place due to its homoiconicity. There 
could be some nice approximations but the devil is in the details. That all 
made me so grateful for what we have and I stopped complaining :-) ... 

Ideally, I wish that `clojure-mode` adapts to the style of given project and 
helps to format my changes accordingly. Again, probably not so easy to do 
either.

Best regards,
Andy
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Clojure Style Guide

[Bozhidar Batsov]

On December 21, 2014 at 1:12:10 AM, Leon Grapenthin (grapenthinl...@gmail.com) 
wrote:
Thanks for bringing this up here and linking to the issue I raised on GH. I 
wanted to start a discussion here as well but have not yet found time. 

My concerns and worries are less about the style-guide in general and more 
about the indentation change regarding assoc introduced as default in 
clojure-mode 4.0.0. 

At this point in the discussion (bbatsovs reply here) I don't think there is 
another way to change his mind than more people in the community trying to 
convince him otherwise.


TLDR is that bbatsov has decided with release 4.0.0 that indenting assoc in the 
way introduced more than 6 years ago is not so much of a good idea anymore 
because it "defies an extremely strong Lisp tradition ". 
I believe I presented a bit more arguments than that. :-)


I find it personally preferable for the three reasons listed here.

Since bbatsov was so kind to fix threading macros yesterday, I guess he can be 
convinced about assoc, too.

This is unlikely to happen. Few people were upset about the assoc indentation 
and more greeted it. Not to mention most tools don’t use special indentation 
for assoc by default. I’ll extend the clojure-mode docs with more info about 
indentation customizations, which sounds like a reasonable compromise to me for 
people who disagree with the defaults. People should certainly be able to 
indent their code however they see fit.



Regarding the discussion in general: How about agreeing to an EDN structure 
with indentation hints which can be loaded into any Clojure IDE? This would 
offer library authors to provide indentation hints for their macros themselves. 
They could also be added as meta-data to the vars so that during an active 
nrepl connection the correct indentation for e. g. om/dom forms would be pulled 
automatically...

Best regards, 
Leon.


On Saturday, December 20, 2014 10:14:18 AM UTC+1, Colin Fleming wrote:
Hi everyone,

There's been a bit of discussion recently on a couple of clojure-mode tickets 
that I thought were worth discussing here. The tickets are #265 and #266, and 
they later led to PR #96 on Bozhidar Batsov's Clojure Style Guide. The part of 
the discussion I wanted to raise starts here, where there's some discussion 
around the nature of the style guide itself.

Bozhidar clearly sees himself as the steward of a community style guide, 
something he's done to great success with the Ruby style guide. However it 
seems that there is a significant part of the community that didn't see it that 
way, and had seen it more as his personal style guide that he happened to put 
out there. I'm interested in starting a discussion around this because I do 
think it's valuable to have some degree of community consensus around these 
issues, specifically so that tools can have consistent defaults.

That said, one of the defining features of lisps in general is that they permit 
essentially unlimited flexibility, and in my experience programmers in general 
really don't like being told what to do, especially around indentation. So, I'd 
like to ask the obvious initial question - do we as a community think that 
there is value in having a style guide like this? If so, to Marshall's point on 
the list, do we think it should try to mandate what people should be doing, or 
should it describe what they actually currently do in real code, even if that's 
the result of historical accidents?

For what it's worth, from my point of view I definitely think that a guide like 
this is useful, and I've referred to Bozhidar's guide myself from time to time 
when trying to decide what to do for a particular feature in Cursive. However I 
do think that it needs more flexibility than it currently has - there are some 
things marked in there as "bad" that I'd like to see downgraded to "prefer the 
other way unless you have a good reason", which of course I always feel like I 
have. In particular, some of the reasoning behind the linked changes above I 
think needs to be more flexible - there are good use cases for customising 
indentation for some functions, for example.

Of course, if we decide that we do want a guide like this then we can spend 
many happy years arguing about what should go in it, but first things first :-)

Cheers,
Colin
--
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://group

[ANN] CIDER 0.13 (California) is out!

[Bozhidar Batsov]

Hey everyone,

In the middle of the summer (for my part of the world, at least) we've got
a hot new CIDER release for you. It's named after my beloved Republic of
California, where its development began. Here are the highlights for the
release:

### New Features

* Add an option `nrepl-prompt-to-kill-server-buffer-on-quit` to control
whether killing nREPL server buffer and process requires a confirmation
prompt.
* [#1672](https://github.com/clojure-emacs/cider/issues/1672): Allow
setting a preferred build tool when multiple are found via
`cider-preferred-build-tool`.
* Ensure Clojure version meets minimum supported by CIDER (1.7.0).
* Fringe indicators highlight which sexps have been loaded. Disable it with
`cider-use-fringe-indicators`.
* New command: `cider-inspect-last-result`.
* `cider-cljs-lein-repl` now also supports figwheel.
* Option `cider-jack-in-auto-inject-clojure` enables the user to specify a
  version of Clojure for CIDER. This allows the user to override the version
  used in a project, particular if it is lower than minimum required for
CIDER.
* Allow the ns displayed by eldoc to be tailored via
`cider-eldoc-ns-function`.
* After connecting a ClojureScript REPL, CIDER will try to figure out if
it's being served on a port and will offer to open it in a browser.
* [#1720](https://github.com/clojure-emacs/cider/issues/1720): Add a
command `cider-eval-sexp-at-point` to evaluate the form around point (bound
to `C-c C-v v`).
* [#1564](https://github.com/clojure-emacs/cider/issues/1564): CIDER's
internal namespaces and vars are filtered from the ns-browser and apropos
functions.
* [#1725](https://github.com/clojure-emacs/cider/issues/1725): Display
class names in eldoc for interop forms.
* [#1572](https://github.com/clojure-emacs/cider/issues/1572): Add support
for variables in eldoc.
* [#1736](https://github.com/clojure-emacs/cider/issues/1736): Show "See
Also" links for functions/variables in documentation buffers.
* [#1767](https://github.com/clojure-emacs/cider/issues/1767): Add a
command `cider-read-and-eval-defun-at-point` to insert the defun at point
into the minibuffer for evaluation (bound to `C-c C-v .`).
* [#1646](https://github.com/clojure-emacs/cider/issues/1646): Add an
option `cider-apropos-actions` to control the list of actions to be applied
on the symbol found by an apropos search.
* [#1783](https://github.com/clojure-emacs/cider/issues/1783): Put eval
commands onto single map bound to `C-c C-v`.
* [#1804](https://github.com/clojure-emacs/cider/issues/1804): Remember
cursor position between `cider-inspector-*` operations.

### Changes

* Simpler keybindings in macroexpand buffer. Expand one step with `m` and
all expansions with `a`. Previously was `C-c C-m` and `C-c M-m`.
* Signal an error sooner if the user misconfigured `cider-known-endpoints`.
* `cider-inspect-read-and-inspect` is obsolete. Use
`cider-inspect-expression` instead.
* Extremely long overlays are truncated and `cider-inspect-last-result` is
recommended.
* Signal `user-error` instead of `error` on jack-in if a project type is
not supported.
* Users with `boot.sh` instead of `boot` should customize
`cider-boot-command` instead of relying on automatic detection.
* [#1737](https://github.com/clojure-emacs/cider/issues/1737): Show value
of locals in debugger tooltip.
* Rebind `cider-eval-last-sexp-and-replace` to `C-c C-v w`.
* Rebind `cider-eval-region` to `C-c C-v r`.
* Rebind `cider-eval-ns-form` to `C-c C-v n`.
* [#1577](https://github.com/clojure-emacs/cider/issues/1577): Show first
line of docstring in ns browser.
* `cider-repl-closing-return` (`C-`) now also completes brackets
(`[]`) and curly braces (`{}`) in an expression.

### Bugs fixed

* [#1755](https://github.com/clojure-emacs/cider/issues/1755): Impossible
completion for multiple zombie REPL buffers.
* [#1712](https://github.com/clojure-emacs/cider/issues/1712): Bad
compilation issue caused when installed along with `nim-mode`.
* Fix arglist display for `def` in the doc buffer.
* Use `cider-apropos-select` instead of `cider-apropos` in
`cider-apropos-documentation-select`.
* [#1561](https://github.com/clojure-emacs/cider/issues/1561): Use an
appropriate font-lock-face for variables, macros and functions in
the ns-browser.
* [#1708](https://github.com/clojure-emacs/cider/issues/1708): Fix
`cider-popup-buffer-display` when another frame is used for the error
buffer.
* [#1733](https://github.com/clojure-emacs/cider/pull/1733): Better error
handling when no boot command is found in `exec-path`.
* Fix orphaned nrepl-messages buffer after `cider-quit`.
* [#1782](https://github.com/clojure-emacs/cider/issues/1782): Disable
mouse-over tooltips when `help-at-pt-display-when-idle` is non-nil.
* [#1811](https://github.com/clojure-emacs/cider/issues/1811): Handle
properly jack-in commands with spaces in them.

Thanks to everyone who made this release possible! I really appreciate all
of your help and hard work!

Enjoy!

*P.S.* I've heard a rumour that asking people

Re: CIDER: function definition is void: nrepl-current-connection-buffer

[Bozhidar Batsov]

A long time ago this function was renamed to cider-current-connection.

On 30 September 2016 at 00:56,  wrote:

> How do I inspect and resolve the following? (Thanks in advance for any
> help)
>
> I did M-x cider-jack-in-clojurescript with CIDER from MELPA stable as
> well as MELPA and got the same result.
>
> I was thinking perhaps I have inconsistent versions of things, or perhaps
> I have something that's out-dated. Here's some of the emacs packages I have
> installed:
>
> egrep "cider|clojure|clj|repl" packages | grep installed
>
>   ac-nrepl   0.21
>   cider  20160927.2135
>   cider-eval-sexp-fu 1.1
>   cljsbuild-mode 0.2.0
>   clojure-cheatsheet 0.4.0
>   clojure-mode   5.5.2
>   clojure-mode-ex... 5.5.2
>   clojurescript-mode 0.5
>   flycheck-clojure   20160704.1221
>   typed-clojure-mode 1.0.0
>
> M-x cider-jack-in-clojurescript
>
> Starting nREPL server via /home/user/bin/lein update-in :dependencies conj
> \[org.clojure/tools.nrepl\ \"0.2.12\"\] -- update-in :plugins conj
> \[cider/cider-nrepl\ \"0.13.0\"\] -- repl :headless...
> nREPL server started on 37596
> [nREPL] Establishing direct connection to localhost:37596 ...
> [nREPL] Direct connection established
> Connected.  nREPL server is up, CIDER REPL is online!
> *error in process filter: ac-nrepl-refresh-class-cache: Symbol's function
> definition is void: nrepl-current-connection-buffer*
> *error in process filter: Symbol's function definition is void:
> nrepl-current-connection-buffer*
>
> ;; Connected to nREPL server - nrepl://localhost:37596
> ;; CIDER 0.14.0snapshot (package: 20160927.2135) (California), nREPL 0.2.12
> ;; Clojure 1.8.0, Java 1.8.0_45
> user>
>
> *~/.lein/profiles.clj* says
>
> {:user {:plugins [[org.clojure/clojure "1.8.0"]]}}
>
> Here's my *project.clj*. I took out references to nrepl but that did not
> resolve the issue.
>
> (defproject foo "0.1.0-SNAPSHOT"
>   :description "FIXME: write this!"
>   :url "http://example.com/FIXME";
>   :license {:name "Eclipse Public License"
> :url "http://www.eclipse.org/legal/epl-v10.html"}
>
>   :min-lein-version "2.6.1"
>
>   :dependencies [[org.clojure/clojure "1.8.0"]
>  [org.clojure/clojurescript "1.9.229"]
>  [org.clojure/core.async "0.2.385"
>   :exclusions [org.clojure/tools.reader]]
>  [prismatic/dommy "1.1.0"]]
>
>   :plugins [[lein-figwheel "0.5.8"]
> [lein-cljsbuild "1.1.4" :exclusions [[org.clojure/clojure
>
>   :source-paths ["src"]
>
>   :clean-targets ^{:protect false} ["resources/public/js/compiled"
> "target"]
>
>   :cljsbuild {:builds
>   [{:id "test"
> :source-paths ["src" "test"]
> :compiler {:output-to  "resources/test/compiled.js"
>:output-dir "resources/test/js/compiled/out"
>:optimizations :whitespace
>:pretty-print true}}
>{:id "dev"
> :source-paths ["src" "test" "cljs_src"]
> :figwheel {:on-jsload "foo.test/run"
>:open-urls ["http://localhost:3449/index.html
> "]}
>
> :compiler {:main foo.core
>:asset-path "js/compiled/out"
>:output-to  "resources/public/js/
> compiled/foo.js"
>:output-dir "resources/public/js/compiled/out"
>:source-map-timestamp true
>:preloads [devtools.preload]}}
>{:id "min"
> :source-paths ["src"]
> :compiler {:output-to "resources/public/js/compiled/
> foo.js"
>:main foo.core
>:optimizations :advanced
>:pretty-print false}}]
>   :test-commands {"test" ["phantomjs"
>   "resources/test/test.js"
>   "resources/test/test.html"]}}
>
>   :figwheel {:css-dirs ["resources/public/css"]}
>
>   :profiles {:dev {:dependencies [[binaryage/devtools "0.7.2"]
>   [figwheel-sidecar "0.5.7"]
>   [com.cemerick/piggieback "0.2.1"]]
>:source-paths ["src" "dev" "cljs_src"]
>:repl-options {:init (set! *print-length* 50)
>   :nrepl-middleware
> [cemerick.piggieback/wrap-cljs-repl]}}})
>
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this mess

Re: CIDER: function definition is void: nrepl-current-connection-buffer

[Bozhidar Batsov]

Ah, noticed your problem - ac-nrepl is a legacy package that hasn't been
updated in ages. There's ac-cider now.

On 30 September 2016 at 09:37, Bozhidar Batsov  wrote:

> A long time ago this function was renamed to cider-current-connection.
>
> On 30 September 2016 at 00:56,  wrote:
>
>> How do I inspect and resolve the following? (Thanks in advance for any
>> help)
>>
>> I did M-x cider-jack-in-clojurescript with CIDER from MELPA stable as
>> well as MELPA and got the same result.
>>
>> I was thinking perhaps I have inconsistent versions of things, or perhaps
>> I have something that's out-dated. Here's some of the emacs packages I have
>> installed:
>>
>> egrep "cider|clojure|clj|repl" packages | grep installed
>>
>>   ac-nrepl   0.21
>>   cider  20160927.2135
>>   cider-eval-sexp-fu 1.1
>>   cljsbuild-mode 0.2.0
>>   clojure-cheatsheet 0.4.0
>>   clojure-mode   5.5.2
>>   clojure-mode-ex... 5.5.2
>>   clojurescript-mode 0.5
>>   flycheck-clojure   20160704.1221
>>   typed-clojure-mode 1.0.0
>>
>> M-x cider-jack-in-clojurescript
>>
>> Starting nREPL server via /home/user/bin/lein update-in :dependencies
>> conj \[org.clojure/tools.nrepl\ \"0.2.12\"\] -- update-in :plugins conj
>> \[cider/cider-nrepl\ \"0.13.0\"\] -- repl :headless...
>> nREPL server started on 37596
>> [nREPL] Establishing direct connection to localhost:37596 ...
>> [nREPL] Direct connection established
>> Connected.  nREPL server is up, CIDER REPL is online!
>> *error in process filter: ac-nrepl-refresh-class-cache: Symbol's function
>> definition is void: nrepl-current-connection-buffer*
>> *error in process filter: Symbol's function definition is void:
>> nrepl-current-connection-buffer*
>>
>> ;; Connected to nREPL server - nrepl://localhost:37596
>> ;; CIDER 0.14.0snapshot (package: 20160927.2135) (California), nREPL
>> 0.2.12
>> ;; Clojure 1.8.0, Java 1.8.0_45
>> user>
>>
>> *~/.lein/profiles.clj* says
>>
>> {:user {:plugins [[org.clojure/clojure "1.8.0"]]}}
>>
>> Here's my *project.clj*. I took out references to nrepl but that did not
>> resolve the issue.
>>
>> (defproject foo "0.1.0-SNAPSHOT"
>>   :description "FIXME: write this!"
>>   :url "http://example.com/FIXME";
>>   :license {:name "Eclipse Public License"
>> :url "http://www.eclipse.org/legal/epl-v10.html"}
>>
>>   :min-lein-version "2.6.1"
>>
>>   :dependencies [[org.clojure/clojure "1.8.0"]
>>  [org.clojure/clojurescript "1.9.229"]
>>  [org.clojure/core.async "0.2.385"
>>   :exclusions [org.clojure/tools.reader]]
>>  [prismatic/dommy "1.1.0"]]
>>
>>   :plugins [[lein-figwheel "0.5.8"]
>> [lein-cljsbuild "1.1.4" :exclusions [[org.clojure/clojure
>>
>>   :source-paths ["src"]
>>
>>   :clean-targets ^{:protect false} ["resources/public/js/compiled"
>> "target"]
>>
>>   :cljsbuild {:builds
>>   [{:id "test"
>> :source-paths ["src" "test"]
>> :compiler {:output-to  "resources/test/compiled.js"
>>:output-dir "resources/test/js/compiled/out"
>>:optimizations :whitespace
>>:pretty-print true}}
>>{:id "dev"
>> :source-paths ["src" "test" "cljs_src"]
>> :figwheel {:on-jsload "foo.test/run"
>>:open-urls ["http://localhost:3449/index.html
>> "]}
>>
>> :compiler {:main foo.core
>>:asset-path "js/compiled/out"
>>:output-to  "resources/public/js/compiled
>> /foo.js"
>>:output-dir "resources/public/js/compiled/out"
>>:source-map-timestamp true
>>:preloads [devtools.preload]}}
>>{:id "min"
>> :source-paths ["src"]
>> :compiler {:output-to "resources/public/js/compiled/
>> foo.js"
>>  

Re: Hacktoberfest labeled issues

[Bozhidar Batsov]

CIDER is participating in this -
https://github.com/clojure-emacs/cider/issues?q=is%3Aissue+is%3Aopen+label%3AHacktoberfest

On 4 October 2016 at 11:28, Karim SENHAJI  wrote:

> Hi all,
>
> Hacktoberfest  is currently
> running in Github (contribute to OSS and win a t-shirt).
> Maybe open-source maintainers could tag there ready/low-hanging fruit
> issues to be part of this event:
> https://github.com/search?l=Clojure&q=state%3Aopen+label%
> 3Ahacktoberfest&ref=advsearch&type=Issues&utf8=%E2%9C%93
>
> I am thinking of projects such as clojars who already have several issues
> ready.
> I am new to the Clojure ecosystem and would love to discover some projects
> via this medium.
>
> Best regards,
> Karim
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Re-launching Expectations!

[Bozhidar Batsov]

Great news!

Looking forward to adding the support for the clojure.test protocol.
CIDER's users will really appreciate it!

On 6 October 2016 at 21:36, Colin Yates  wrote:

> Thanks Sean.
>
> On 6 October 2016 at 19:03, Sean Corfield  wrote:
> >> is there a 'benefits over clojure.test' blog anywhere?
> >
> > Not that I’m aware of. I added a GH issue against the website content
> for that. Jay wrote a series of blog posts about Expectations back in 2011
> that included the justification for it:
> >
> > http://blog.jayfields.com/2011/11/clojure-expectations-introduction.html
> >
> >> I wonder if it is the benefits are more subjective
> >
> > Yes, I find the BDD-style of Expectations much more to my liking than
> the assertive style of clojure.test – the latter feels very imperative to
> me. So there’s definitely an element of stylistic preference at play here.
> >
> >> I personally like the names I give to tests etc.
> >
> > Jay has an opinion on that – see http://blog.jayfields.com/
> 2011/11/clojure-expectations-unit-testing-wrap.html
> >
> > I’m split on the topic. There’s a practical reason for giving tests
> names, and that relates to tooling and, in particular, what CIDER and other
> tools expect (and in fact that is what has triggered this whole
> re-launching: in order to better support tooling at large, Expectations
> needs to provide a way to give predictable names to tests so that tooling
> can run and re-run individual tests).
> >
> > Sean
> >
> >
> >
> > --
> > 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 new members are moderated - please be patient with
> your first post.
> > To unsubscribe from this group, send email to
> > clojure+unsubscr...@googlegroups.com
> > For more options, visit this group at
> > http://groups.google.com/group/clojure?hl=en
> > ---
> > You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to clojure+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] CIDER 0.14 (Berlin) released

[Bozhidar Batsov]

Hey everyone,

Yesterday I released CIDER 0.14 (Berlin). It's a rather small CIDER update,
mostly focusing on bug fixes. Thanks to everyone who contributed to this
release!

The release notes are here
https://github.com/clojure-emacs/cider/releases/tag/v0.14.0

Enjoy!

P.S. Once again I'd like to solicit more contributions to the project from
the CIDER community. I haven't been able to find a lot of time for the
project lately (and this has been the case with other prominent team
members as well). As a result a ton of issues have piled on (
https://github.com/clojure-emacs/cider/issues). Help me clean up the
tracker and make CIDER better! :-)

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: error in nrepl

[Bozhidar Batsov]

Newer versions of CIDER are much easier to setup than the older ones (e.g.
they auto-inject their dependencies, so you don't have to fiddle with
profiles.clj). You should try the latest stable or dev release. That said
you can also check Monroe (https://github.com/sanel/monroe) which is a fork
of a very old version of CIDER (from around the time it was named nrepl.el)
or inf-clojure (https://github.com/clojure-emacs/inf-clojure) - a
completely 0-setup Clojure(Script) REPL with support for connecting to a
REPL socket server.

On 24 June 2017 at 00:36,  wrote:

>
> Yes, sadly, I've never gotten Cider to work with Emacs. I keep thinking
> someday I'll take a weekend and work through all the errors and get it
> working, but I never seem to find the time. So I keep working with an old
> version of nrepl. But I take it, from your answer, you think this error
> would vanish if I upgraded to Cider?
>
>
>
>
> On Friday, June 23, 2017 at 5:15:09 PM UTC-4, James Reeves wrote:
>>
>> nrepl-jack-in? Do you mean cider-jack-in? AFAIK nrepl-jack-in is from a
>> very old version of Cider.
>>
>> On 23 June 2017 at 21:29,  wrote:
>>
>>> I'm using Emacs on my Mac. I ran "nrepl-jack-in" to load up the repl.
>>> I'm iterating over a dataset from mysql. My code is very simple, I'm just
>>> trying to count the words:
>>>
>>> (reduce
>>>
>>> (fn [map-of-word-count next-name]
>>> (let [
>>> words (clojure.string/split next-name #"\s")
>>> map-of-names-words-with-count (frequencies words)
>>> ]
>>> (println map-of-names-words-with-count)
>>> (merge-with + map-of-word-count map-of-names-words-with-count)
>>> )
>>> )
>>> {}
>>> names)
>>>
>>> I keep getting this message:
>>>
>>>
>>> error in process filter: nrepl-bdecode-buffer: Cannot decode object: 1
>>> error in process filter: Cannot decode object: 1
>>> Error running timer `jit-lock-stealth-fontify': (error "Variable binding
>>> depth exceeds max-specpdl-size")
>>> timer-relative-time: Variable binding depth exceeds max-specpdl-size
>>>
>>>
>>> Does anyone know what this means?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To post to this group, send email to clo...@googlegroups.com
>>> Note that posts from new members are moderated - please be patient with
>>> your first post.
>>> To unsubscribe from this group, send email to
>>> clojure+u...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/clojure?hl=en
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to clojure+u...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> James Reeves
>> booleanknot.com
>>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrating nREPL out of Clojure Contrib

[Bozhidar Batsov]

Contrib projects do not accept pull requests. They accept only patches
submitted via JIRA.

On Wed, Jul 19, 2017 at 09:11 Didier  wrote:

> I'm not too familiar with the way contribs are managed, isn't tools.nrepl
> repo in github? Wouldn't the only step to contribute be to sign the CA and
> send a pull request of your changes?
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] CIDER 0.15 (London)

[Bozhidar Batsov]

Hey everyone,

Just in the time for EuroClojure 2017, we've released a major update to
CIDER - the popular Clojure interactive development environment, built on
top of Emacs and nREPL.

The big news is that CIDER 0.15 ships with a lot of features related to
clojure.spec and that the debugger is now much more robust than it used to
be in previous releases!

As usual - there are many other small new features, improvements and
bugfixes. Go over the release notes for all the details!

Enjoy CIDER 0.15 (responsibly) and have a lot of fun at EuroClojure!

### New Features

* [#2050](https://github.com/clojure-emacs/cider/pull/2050) Use `view-mode`
for `cider-grimoire` buffers
* Make stacktraces and other location references in REPL clickable.
* Highlight root namespace in REPL stacktraces.
* Filter stacktrace to just frames from your project.
* [#1918](https://github.com/clojure-emacs/cider/issues/1918): Add new
commands `cider-browse-spec` and `cider-browse-spec-all` which start a spec
browser.
* [#2015](https://github.com/clojure-emacs/cider/pull/2015): Show symbols
as special forms *and* macros in `cider-doc`
* [#2012](https://github.com/clojure-emacs/cider/pull/2012): Support
special forms in `cider-apropos` and `cider-grimoire-lookup`.
* [#2007](https://github.com/clojure-emacs/cider/pull/2007): Fontify code
blocks from `cider-grimoire` if possible.
* Add support for notifications from the NREPL server.
* [#1990](https://github.com/clojure-emacs/cider/issues/1990): Add new
customation variable `cider-save-files-on-cider-refresh` to allow
auto-saving buffers when `cider-refresh` is called.
* Add new function `cider-load-all-files`, along with menu bar update.
* Add new customization variable `cider-special-mode-truncate-lines`.
* Add an option `cider-inspector-fill-frame` to control whether the cider
inspector window fills its frame.
* [#1893](https://github.com/clojure-emacs/cider/issues/1893): Add negative
prefix argument to `cider-refresh` to inhibit invoking of
cider-refresh-functions
* [#1776](https://github.com/clojure-emacs/cider/issues/1776): Add new
customization variable `cider-test-defining-forms` allowing new test
defining forms to be recognized.
* [#1860](https://github.com/clojure-emacs/cider/issues/1860): Add
`cider-repl-history` to browse the REPL input history and insert elements
from it into the REPL buffer.
* Add new customization variable `cider-font-lock-reader-conditionals`
which toggles syntax highlighting of reader conditional expressions based
on the buffer connection.
* Add new face `cider-reader-conditional-face` which is used to mark unused
reader conditional expressions.
* [#1544](https://github.com/clojure-emacs/cider/issues/1544): Add a new
defcustom `nrepl-use-ssh-fallback-for-remote-hosts` to control the behavior
of `nrepl-connect` (and in turn that of `cider-connect`) for remote hosts.
* [#1910](https://github.com/clojure-emacs/cider/issues/1910): Add custom
company-mode completion style to show fuzzy completions from Compliment.
* Introduce `cider-*-global-options` for customizing options that are not
related to tasks.
* [#1731](https://github.com/clojure-emacs/cider/issues/1731): Change code
in order to use the new `cider.tasks/add-middleware` boot tasks.
* [#1943](https://github.com/clojure-emacs/cider/pull/1943): Add
interactive function to flush Compliment caches.
* [#1726](https://github.com/clojure-emacs/cider/issues/1726): Order keys
in printed nrepl message objects.
* [#1832](https://github.com/clojure-emacs/cider/issues/1832): Add new
customization variable `cider-eldoc-display-context-dependent-info` to
control showing eldoc info for datomic query input parameters.
* Make it possible to disable auto-evaluation of changed ns forms via the
defcustom `cider-auto-track-ns-form-changes`.
* [#1991](https://github.com/clojure-emacs/cider/issues/1832): Make it
possible to disable the prompt to open a ClojureScript in a browser on
connect via `cider-offer-to-open-cljs-app-in-browser`.
* [#1995](https://github.com/clojure-emacs/cider/pull/1995): Add new
customization variable `cider-doc-auto-select-buffer` to control cider-doc
popup buffer auto selection.
* Ensure that `cider-current-connection` picks the most recently used
connection in ambiguous cases.
* Ensure that `cider-switch-to-repl-buffer` picks the most recent repl
buffer if multiple connections are available.
* Add new function `cider-project-connections-types`.

### Changes

* Handle ANSI REPL evaluation created by Puget.
* Drop support for Emacs 24.3.
* Don't try to use ssh automatically when connecting to remote hosts and a
direct connection fails. See `nrepl-use-ssh-fallback-for-remote-hosts`.
* [#1945](https://github.com/clojure-emacs/cider/pull/1945): Start nREPL
servers bound to `::` by default using `cider-jack-in`.
* Renamed `cider-prompt-save-file-on-load` to `cider-save-file-on-load` and
adjust its supported values accordingly (the default now is `'prompt` and
`'always-save` is now simply `t`).
* [#2014

Re: Migrating nREPL out of Clojure Contrib

[Bozhidar Batsov]

On 20 July 2017 at 08:14, Sean Corfield  wrote:

> At the risk of being unpopular… 😊
>
>
>
> I think there are quite a few people who _*say*_ that it’s an obstacle to
> their contributing to Clojure or to a Contrib library but in reality they
> wouldn’t actually contribute anyway, so it becomes an excuse.
>
>
>
> For example, I’ve seen many people over the years complain about needing
> to sign a CA and submit a patch in order to update the documentation that
> is part of a project. Years ago, I moved all the documentation for
> clojure.java.jdbc off to clojure-doc.org where anyone can create issues
> and submit PRs because it’s “just” a GitHub project. Despite removing all
> the supposed “barriers to entry”, there have been almost zero community
> contributions of any sort to that documentation (with one recent exception:
> huge thank you to ehashman for some great work submitted recently!).
>

I think few people can doubt my contributions to OSS projects, but I value
my time too much to waste it on JIRA and updating patches like crazy there.
Raising the barrier to entry to basic projects like nREPL and
clojure.java.jdbc seems pointless to me. It might make sense for Clojure,
but it certainly doesn't make much sense for anything else.

Giving a documentation example is unfair - how many developers fond of
writing documentation do you know? Most of my bigger OSS projects are
getting a ton of contributions from all sorts of people.

>
>
> A lot of big, well-known FOSS projects require a signed CA and have very
> specific contributing processes. Either folks will contribute or they
> won’t. I find it hard to believe that nREPL will suddenly get a stream of
> contributions that it wouldn’t get if it continues as a Contrib project.
> Hundreds of people have signed CAs on file – there’s a good pool of people
> who could, easily, contribute to nREPL already.
>
>
>
> Forking, renaming, and rebooting a fundamental bedrock project like nREPL
> could be very risky, and could cause a lot of pain/churn for a lot of
> Clojure users out there.
>

Let's be honest - Chas is basically the only nREPL dev, so it seems to me
that all we need to have a painless transition is his blessing of a
fork/reboot. The pain would be mostly updating deps in projects like lein
and boot. CIDER is one of the projects with biggest commitment to nREPL
(and we've been behind many bugfixes and small improvements in recent
years) and we'd support a fork/reboot 100%.

>
>
> (or of course you could all prove me wrong and it might be a painless
> transition and nREPL might flourish in ways none of us could possibly have
> imagined so far…)
>
>
>
> Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
> An Architect's View -- http://corfield.org/
>
> "If you're not annoying somebody, you're not really alive."
> -- Margaret Atwood
>
>
>
> *From: *Didier 
> *Sent: *Wednesday, July 19, 2017 9:43 PM
> *To: *Clojure 
> *Subject: *Re: Migrating nREPL out of Clojure Contrib
>
>
>
> So do we have any idea of contributions are not made because of the CA or
> Jira?
>
> I understand it's hard to estimate how many people were discouraged by
> this. Maybe it should be part of the Clojure survey nexr time.
>
> Were you ever discouraged to contribute to a Contrib lib because of Jira?
>
> Were you ever discouraged to contribute to a Contrib lib because of the CA?
>
> I feel like without more data into these, it's only speculative that
> changes to nRepl would result in more active contributions from the
> community.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message be

Re: Migrating nREPL out of Clojure Contrib

[Bozhidar Batsov]

On 18 July 2017 at 15:48, Chas Emerick  wrote:

> Hi all,
>
> I've been approached many, many times over the years (and more frequently
> since the development and inclusion of socket-repl) about the potential of
> moving nREPL[1] out of clojure contrib…either back to its original
> location[2], or under one of the various Clojure community organizations.
> I've generally demurred or ghosted on these suggestions, sometimes out of a
> lack of time/attention, and often out of just not wanting to stir the pot.
> The pace of them has quickened somewhat lately though, and I'd like to put
> the whole topic to bed and hopefully get the project to a better footing in
> the process.
>
> First, to stipulate a few things:
>
>1. nREPL is an essential bit of infrastructure in Clojure tooling
>2. On balance, I have neglected the project in recent years, to the
>detriment of all of the users of the aforementioned tooling.
>3. On balance, contributors and potential contributors have been less
>involved (or turned away entirely) because of the well-known friction that
>comes with the contrib process and requirements. (tbh, this is a factor in
>#2, though not the majority)
>4. No one (least of all me) would object to nREPL having its
>contribution process managed through github or gitlab.
>
> So basically everyone wants nREPL to be a "regular" project, and subject
> to and beneficiary of the same expectations as 99.9% of all of the other
> OSS projects we all interact with daily. How does that happen?
>
>
> The only routes AFAICT are:
>
>1. to fork back elsewhere, which would require keeping the EPL license
>and copyright assignment of the current codebase. Literally anyone can do
>this at any time, without any coordination with anyone else.
>2. for me to reboot the project. This would not be difficult given I
>"own" the vast majority of the project's commits. This would allow for the
>elimination of the copyright assignment, and potentially a different
>license (I'm partial to MPLv2, but we'll see). If this route is taken, we
>could set up a project issue where the other contributors of nontrivial
>patches could agree (or not) to the reconstitution of their code w/o the
>copyright assignment, etc.
>
> In either case, this "new" nREPL project's artifacts would end up being
> distributed under a different maven groupId (`com.cemerick`, if I'm to
> continue deploying, etc). The clojure-contrib nREPL project remain, and any
> releases that are done from it after the fork/reboot would continue to be
> under the `org.clojure` coordinates. Downstream projects need to choose
> whether or not to change dependencies; I'd expect the vast majority of
> future motion to gravitate to the reboot, but that's just speculation at
> this point.
>
>
> I would like to hear *here* (no more private mails, please! :-) from any
> nREPL users, contributors, etc. As much as possible, I would like *not *to
> debate/re-litigate the merits of contrib and its process here; let's focus
> on what steps will yield the best outcome for nREPL and its stakeholders.
>

My vote is for a project reboot spearheaded by you. I doubt people would
have objections to the relicensing of the project and I promise to help as
much as I can if the project gets "freed" from the shackles of contrib.

I do thing it might make sense for the project to be housed under a nREPL
org on github, which can also house related important middleware and
potentially client libraries for different languages.

>
> Thanks!
>
>
> - Chas
>
> [1] https://github.com/clojure/tools.nrepl/
> [2] https://github.com/cemerick/nrepl
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cl

Re: Migrating nREPL out of Clojure Contrib

[Bozhidar Batsov]

So, what's the next step here?

On 23 July 2017 at 02:16, Colin Fleming  wrote:

> Are you saying the contrib process is deliberatly made to be difficult for
>> the community to contribute to it?
>
>
> No, not at all, just that it's deliberately designed to be exactly the way
> it is, so dedicating a lot of time to trying to change that is likely to be
> frustrating and fruitless.
>
> I agree about the confusion of a lot of the contrib projects, I'm often
> unsure if they're abandoned or just mature. I don't know if the expectation
> or the reality is that they should all be in a working state.
>
> On 23 July 2017 at 09:17, Didier  wrote:
>
>> > The contrib process is in place because some want it that way - it's
>> very deliberately by design and AFAICT unlikely to change.
>>
>> Are you saying the contrib process is deliberatly made to be difficult
>> for the community to contribute to it?
>>
>> If so, maybe if it had more obvious tenets, I find its difficult as a
>> user to understand what the contribs are for, who maintains them, what
>> their status are, and how they differ to the standards library, or other
>> community projects.
>>
>> I can't contribute to OSS, because of my current employment, but as a non
>> contributing Clojure user, I've always wondered how much I should rely on
>> contribs, some of them seem quasi-abandonned, yet they appear more
>> official, and it makes it hard for me to decide if I want to take a
>> dependency on them or not.
>>
>> In a way, an active project gives me more trust, and if taking nRepl out
>> of contrib makes it more active, that's a good thing. Unless contrib libs
>> come with any official support guarantees, or some form of stronger
>> commitments?
>>
>> --
>> 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 new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Clojure 1.9.0-alpha18

[Bozhidar Batsov]

Just for the sake of completeness with regards to the issue in CIDER - it
has been addressed in master and I'll issue a bugfix release soon.

On 24 August 2017 at 05:20, Alex Miller  wrote:

> Correct, this was just something Rich ran into while doing the pluggable
> resolver work. The intent has always been that only aliases were to be
> supported in auto-resolved keyword qualifiers and fully-qualified keywords
> there would accidentally work. The spec and code now *only* support
> aliases.
>
>
>
> On Wed, Aug 23, 2017 at 9:01 PM, Sean Corfield  wrote:
>
>> The breakage in CIDER is a good example of what this change disallows:
>>
>>
>>
>> java.lang.RuntimeException: Invalid token: ::clojure.test/once-fixtures
>>
>>
>>
>> Invalid because clojure.test is not an alias – so it should be
>> :clojure.test/once-fixtures instead (or ::test/once-fixtures). See the
>> source here:
>>
>>
>>
>> https://github.com/clojure-emacs/cider-nrepl/blob/master/src
>> /cider/nrepl/middleware/test.clj#L124-L138
>>
>>
>>
>> Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
>> An Architect's View -- http://corfield.org/
>>
>> "If you're not annoying somebody, you're not really alive."
>> -- Margaret Atwood
>>
>>
>>
>> *From: *Colin Fleming 
>> *Sent: *Wednesday, August 23, 2017 5:59 PM
>> *To: *clojure@googlegroups.com
>> *Subject: *Re: [ANN] Clojure 1.9.0-alpha18
>>
>>
>>
>> Tighten autoresolved keywords and autoresolved namespace map syntax to
>> support *only* aliases, as originally intended
>>
>>
>>
>> What does this mean? Is there a JIRA discussion about this?
>>
>>
>>
>> On 24 August 2017 at 04:03, Alex Miller  wrote:
>>
>> Clojure 1.9.0-alpha18 is now available.
>>
>>
>>
>> Try it via
>>
>>
>>
>> - Download: https://repo1.maven.org/maven2/org/clojure/clojure
>> /1.9.0-alpha18
>>
>> - Leiningen: [org.clojure/clojure "1.9.0-alpha18"]
>>
>>
>>
>> 1.9.0-alpha18 includes the following changes since 1.9.0-alpha17:
>>
>>
>>
>> - Can now bind *reader-resolver* to an impl of LispReader$Resolver to
>> control the reader's use of namespace interactions when resolving
>> autoresolved keywords and maps.
>>
>> - Tighten autoresolved keywords and autoresolved namespace map syntax to
>> support *only* aliases, as originally intended
>>
>> - Updated to use core.specs.alpha 0.1.24
>>
>> --
>> 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 new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> 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 new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> 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 new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Clojure" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/clojure/rb22V98rPLM/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this

Re: Cider - emacs lisp errors reported

[Bozhidar Batsov]

It might have been changed upstream. Not sure what's your Emacs version. A
while ago we backported this macro in whatever its current form was for
compatibility with older Emacsen.

File a ticket on GitHub and we'll investigate.


On 10 December 2017 at 13:44, Peter Hull  wrote:

> I noticed this when updating cider via melpa, and I wasn't sure if it's
> already known about or whether it is even an problem. I thought I'd ask
> here before submitting an issue to github.
>
> Compiling file 
> /Users/peterhull/.emacs.d/elpa/cider-20171209.1602/cider-browse-spec.el
> at Sun Dec 10 11:29:29 2017
> cider-browse-spec.el:277:1:Error: Wrong number of arguments: when-let, 1
>
> Compiling file 
> /Users/peterhull/.emacs.d/elpa/cider-20171209.1602/cider-classpath.el
> at Sun Dec 10 11:29:29 2017
> cider-classpath.el:102:1:Error: Wrong number of arguments: when-let, 1
>
> Compiling file 
> /Users/peterhull/.emacs.d/elpa/cider-20171209.1602/cider-client.el
> at Sun Dec 10 11:29:29 2017
> cider-client.el:143:1:Error: Wrong number of arguments: when-let, 1
>
> Compiling file 
> /Users/peterhull/.emacs.d/elpa/cider-20171209.1602/cider-common.el
> at Sun Dec 10 11:29:29 2017
> cider-common.el:186:1:Error: Wrong number of arguments: when-let, 4
>
> Compiling file 
> /Users/peterhull/.emacs.d/elpa/cider-20171209.1602/cider-compat.el
> at Sun Dec 10 11:29:29 2017
>
> Compiling file 
> /Users/peterhull/.emacs.d/elpa/cider-20171209.1602/cider-debug.el
> at Sun Dec 10 11:29:29 2017
> cider-debug.el:226:1:Error: Wrong number of arguments: when-let, 1
>
> Compiling file /Users/peterhull/.emacs.d/elpa/cider-20171209.1602/cider-doc.el
> at Sun Dec 10 11:29:29 2017
> cider-doc.el:263:1:Error: Wrong number of arguments: when-let, 1
>
> And for example, the first instance looks like this
>
> (defun cider-browse-spec--browse-at (&optional pos)
>   "View the definition of a spec.
>
> Optional argument POS is the position of a spec, defaulting to point.  POS
> may also be a button, so this function can be used a the button's `action'
> property."
>   (interactive)
>   (let ((pos (or pos (point
> (when-let ((spec (button-get pos 'spec-name)))
>   (cider-browse-spec--browse spec
>
> I am not an elisp expert but I think the syntax of when-let is (when-let
> (var value) body) rather than (when-let ((var value)) body)
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] CIDER 0.16 (Riga)

[Bozhidar Batsov]

Hey everyone,

Here's one (a bit overdue) Christmas present for all of you - a major
update to CIDER, the popular Clojure interactive development environment,
built on top of Emacs and nREPL.

The big news is that CIDER 0.16 starts much faster when you use
`cider-jack-in` (due to deferred loading of most of the nREPL middleware
that CIDER uses internally to power its features).
As usual - there are other small new features, improvements and bugfixes.
Go over the release notes for all the details!

Enjoy CIDER 0.16 (ir)responsibly and have an awesome New Year!

P.S. Special thanks to ClojureX's team for helping me find the energy and
the resolve to finish the work on this release and to all the amazing
people who contributed to it! You're awesome! Keep rocking! :-)

P.P.S. We've got plenty of small newcomer-friendly tickets that you can
help with here
https://github.com/clojure-emacs/cider/issues?q=is%3Aissue+is%3Aopen+label%3A%22low+hanging+fruit%22

### New Features

* [#2082](https://github.com/clojure-emacs/cider/pull/2082),
[cider-nrepl#440](https://github.com/clojure-emacs/cider-nrepl/pull/440):
Add specialized stacktraces for clojure.spec assertions.
* [#2111](https://github.com/clojure-emacs/cider/pull/2111): Add
`cider-pprint-eval-last-sexp-to-comment` and
`cider-pprint-eval-defun-to-comment`.
* Add a REPL shortcut for `cider-repl-require-repl-utils` (this makes it
easy to require common functions like `doc`, `source`, etc. in REPL
buffers).
* [#2112](https://github.com/clojure-emacs/cider/issues/2112): Add a new
interactive command `cider-find-keyword` (bound to `C-c C-:`).
* [#2144](https://github.com/clojure-emacs/cider/issues/2144): Create a
Docker image to mimic the Travis CI environment.

### Changes

* `cider-switch-to-last-clojure-buffer` switches to most recent relevant
Clojure(Script) buffer instead of the last "remembered" buffer.
* [cider-nrepl#438](https://github.com/clojure-emacs/cider-nrepl/pull/438):
Improve startup time by deferring loading CIDER's middleware until the
first usage.
* [#2078](https://github.com/clojure-emacs/cider/pull/2078): Improve
startup time by bundling together sync requests during startup.
* `cider-rotate-default-connection` will warn if you use it with only a
single active connection.
* `cider-format-buffer` tries to preserve the point position.

### Bugs Fixed

* [#2084](https://github.com/clojure-emacs/cider/issues/2084): Select
correct REPL type (clj or cljs) in `cider-switch-to-repl-buffer`
conditional on the current buffer.
* [#2088](https://github.com/clojure-emacs/cider/issues/2088): Fix
functions defined with `def` being font-locked as vars instead of functions.
* [#1651](https://github.com/clojure-emacs/cider/issues/1651),
[cider-nrepl#445](https://github.com/clojure-emacs/cider-nrepl/pull/455):
Fix `cider-expected-ns` returns `nil` on boot projects.
* [#2120](https://github.com/clojure-emacs/cider/issues/2120): Fix Travis
CI build errors for Emacs versions >25.2.
* [#2117](https://github.com/clojure-emacs/cider/pull/2117): Ensure
`cider-repl-result-prefix` is only inserted before the first result chunk.
* [#2123](https://github.com/clojure-emacs/cider/issues/2123): Process
properly the Java version in Java 9.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Russ olsen's Clojure Book

[Bozhidar Batsov]

Nice!

Looking forward to reading it! I'm a big fan of your Ruby work!

On 12 January 2018 at 23:29,  wrote:

> So it's been 6 years, 6 months and 19 days but the book is on it's way.
> It's called Getting Clojure, published by the Pragmatic Press:
>
> https://twitter.com/russolsen/status/929096359919214592
>
> Thanks for asking!
>
> Russ
>
> On Wednesday, June 29, 2011 at 11:09:56 PM UTC-4, Sayth Renshaw wrote:
>>
>>
>> Just wanted to put a shout out to Russ Olsen to see what would be
>> needed to get a Russ Olsen book on clojure to happen. I am reading
>> design principles in Ruby and its a great read, I feel I am learning
>> much moe than just Ruby which is why I am reading it.
>>
>> I woould absolutely love to read how Russ would apply these design
>> principles to Clojure a more functional language. His books are all 5
>> star reads(amazon ratings) and would greatly enjoy being able to read
>> a Russ Olsen clojure book.
>>
>> Is there any way we could help this to happen? Is anyone else
>> interested in such a book?
>>
>> Sayth
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: numeric-tower versus clojure 1.9

[Bozhidar Batsov]

I also got a CIDER ticket about pretty much the same problem
https://github.com/clojure-emacs/cider/issues/2169

I guess there's some problem with Clojure 1.9 and the tower, but I'm not
sure about its exact extent.

On 18 January 2018 at 02:41, Alex Miller  wrote:

> I can't reproduce that locally. Checking with the new clojure 1.9 clj tool:
>
> $ echo '{:deps {org.clojure/math.numeric-tower {:mvn/version "0.0.4"}}}'
> > deps.edn
> $ clj
> Clojure 1.9.0
> user=> (require '[clojure.math.numeric-tower :as n])
> nil
> user=> (dir n)
> MathFunctions
> abs
> ceil
> ...
>
>
> On Wednesday, January 17, 2018 at 4:26:44 PM UTC-6, Andrew Dabrowski wrote:
>>
>> Is clojure.math.numeric-tower incompatible with clojure 1.9?  The numeric
>> tower is still at version 0.0.4, 4 years old.  WHen I try to use I get the
>> error
>>
>> 1. Caused by java.io.FileNotFoundException
>>Could not locate clojure/math/numeric_tower__init.class or
>>clojure/math/numeric_tower.clj on classpath. Please check that
>>namespaces with dashes use underscores in the Clojure file name.
>>
>> In particular math.numeric-tower does not seem to obey the
>> dash->underscore convention, nor does the installation seem to include
>> init.class or .clj files.
>>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] clojure tools 1.9.0.315, tools.deps.alpha 0.5.342

[Bozhidar Batsov]

How would you suggest running an nREPL server with clj? I want to use the
new functionality to just inject nREPL and some middleware as deps and
start a REPL server that CIDER could connect to. Basically I want to use it
do something like:

lein update-in :dependencies conj \[org.clojure/tools.nrepl\ \"0.2.13\"\
\:exclusions\ \[org.clojure/clojure\]\] -- update-in :plugins conj
\[cider/cider-nrepl\ \"0.17.0-SNAPSHOT\"\] -- repl :headless :host ::...
(that's how we boot a CIDER compatible repl with leiningen)

I've got a few ideas, but you might know something that I don't.

On 23 January 2018 at 22:37, Alex Miller  wrote:

> clojure tools 1.9.0.315 is now available in brew and via
> https://clojure.org/guides/getting_started
>
> Highlights:
>
>   * NEW -Stree to print dependency tree
>   * NEW -Sdeps to supply a deps.edn on the command line as data
>   * FIX bug with git deps using :deps/root writing File objects to libs
> files
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] clojure tools 1.9.0.315, tools.deps.alpha 0.5.342

[Bozhidar Batsov]

Yeah, I was thinking exactly of this - passing some deps as command-line
args and running some simply script, that we can bundle with CIDER. I was
just wondering if I could do it easy without a script. :-)

At any rate I think that clj will lower the bar to entry significantly for
newcomers, as asking people to install something like lein or boot to start
playing with the language is a bit too much IMO.

On 24 January 2018 at 15:55, Alex Miller  wrote:

> For the deps, you can either create an alias (probably best in
> ~/.clojure/deps.edn):
>
> { ...
>   :aliases
>   {:nrepl
> {:extra-deps
>   {org.clojure/tools.nrepl {:mvn/version “0.2.13”}
>cider/cider-nrepl {:mvn/version “0.17.0-SNAPSHOT”}
>
> Which you’ll activate with clojure -R:nrepl
>
> Or inject them directly on the command line with the new -Sdeps:
>
> clojure -Sdeps “{:deps {org.clojure/tools.nrepl {:mvn/version \“0.2.13\”}
> cider/cider-nrepl {:mvn/version \“0.17.0-SNAPSHOT\”}}}”
>
> Then it’s a matter of figuring out whatever setup you need to run a
> headless nrepl server with the right middleware starting from a main. I’m
> guessing this probably involves a few lines of code. It’s certainly
> possible to handle that through some combination of clojure.main’s -m -i -e
> params or it might be simplest to just write a .clj file and have
> clojure.main execute that.
>
> One of the things in my queue for the next few weeks is a way to create a
> main args alias so that may come in handy if it is possible to do it
> without a script and embed it in the shared aliases.
>
>
> On Jan 24, 2018, at 6:20 AM, Bozhidar Batsov  wrote:
>
> How would you suggest running an nREPL server with clj? I want to use the
> new functionality to just inject nREPL and some middleware as deps and
> start a REPL server that CIDER could connect to. Basically I want to use it
> do something like:
>
> lein update-in :dependencies conj \[org.clojure/tools.nrepl\ \"0.2.13\"\
> \:exclusions\ \[org.clojure/clojure\]\] -- update-in :plugins conj
> \[cider/cider-nrepl\ \"0.17.0-SNAPSHOT\"\] -- repl :headless :host ::...
> (that's how we boot a CIDER compatible repl with leiningen)
>
> I've got a few ideas, but you might know something that I don't.
>
> On 23 January 2018 at 22:37, Alex Miller  wrote:
>
>> clojure tools 1.9.0.315 is now available in brew and via
>> https://clojure.org/guides/getting_started
>>
>> Highlights:
>>
>>   * NEW -Stree to print dependency tree
>>   * NEW -Sdeps to supply a deps.edn on the command line as data
>>   * FIX bug with git deps using :deps/root writing File objects to libs
>> files
>>
>> --
>> 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 new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Clojure" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/clojure/RlHjnJPpFbU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For 

Re: [ANN] clojure tools 1.9.0.315, tools.deps.alpha 0.5.342

[Bozhidar Batsov]

That's exactly what I'm planning to do. Thanks for the help, Alex! And
thanks for working on this!

On 24 January 2018 at 16:25, Alex Miller  wrote:

> If you had a simple main that could be used to do the startup, that could
> also be delivered via an extra dep (even a git dep) and could declare
> tools.nrepl and cider-nrepl as deps itself. Then you would have basically
> one thing you can add and run.
>
> On Wed, Jan 24, 2018 at 8:12 AM, Bozhidar Batsov 
> wrote:
>
>> Yeah, I was thinking exactly of this - passing some deps as command-line
>> args and running some simply script, that we can bundle with CIDER. I was
>> just wondering if I could do it easy without a script. :-)
>>
>> At any rate I think that clj will lower the bar to entry significantly
>> for newcomers, as asking people to install something like lein or boot to
>> start playing with the language is a bit too much IMO.
>>
>> On 24 January 2018 at 15:55, Alex Miller  wrote:
>>
>>> For the deps, you can either create an alias (probably best in
>>> ~/.clojure/deps.edn):
>>>
>>> { ...
>>>   :aliases
>>>   {:nrepl
>>> {:extra-deps
>>>   {org.clojure/tools.nrepl {:mvn/version “0.2.13”}
>>>cider/cider-nrepl {:mvn/version “0.17.0-SNAPSHOT”}
>>>
>>> Which you’ll activate with clojure -R:nrepl
>>>
>>> Or inject them directly on the command line with the new -Sdeps:
>>>
>>> clojure -Sdeps “{:deps {org.clojure/tools.nrepl {:mvn/version
>>> \“0.2.13\”} cider/cider-nrepl {:mvn/version \“0.17.0-SNAPSHOT\”}}}”
>>>
>>> Then it’s a matter of figuring out whatever setup you need to run a
>>> headless nrepl server with the right middleware starting from a main. I’m
>>> guessing this probably involves a few lines of code. It’s certainly
>>> possible to handle that through some combination of clojure.main’s -m -i -e
>>> params or it might be simplest to just write a .clj file and have
>>> clojure.main execute that.
>>>
>>> One of the things in my queue for the next few weeks is a way to create
>>> a main args alias so that may come in handy if it is possible to do it
>>> without a script and embed it in the shared aliases.
>>>
>>>
>>> On Jan 24, 2018, at 6:20 AM, Bozhidar Batsov 
>>> wrote:
>>>
>>> How would you suggest running an nREPL server with clj? I want to use
>>> the new functionality to just inject nREPL and some middleware as deps and
>>> start a REPL server that CIDER could connect to. Basically I want to use it
>>> do something like:
>>>
>>> lein update-in :dependencies conj \[org.clojure/tools.nrepl\ \"0.2.13\"\
>>> \:exclusions\ \[org.clojure/clojure\]\] -- update-in :plugins conj
>>> \[cider/cider-nrepl\ \"0.17.0-SNAPSHOT\"\] -- repl :headless :host ::...
>>> (that's how we boot a CIDER compatible repl with leiningen)
>>>
>>> I've got a few ideas, but you might know something that I don't.
>>>
>>> On 23 January 2018 at 22:37, Alex Miller  wrote:
>>>
>>>> clojure tools 1.9.0.315 is now available in brew and via
>>>> https://clojure.org/guides/getting_started
>>>>
>>>> Highlights:
>>>>
>>>>   * NEW -Stree to print dependency tree
>>>>   * NEW -Sdeps to supply a deps.edn on the command line as data
>>>>   * FIX bug with git deps using :deps/root writing File objects to libs
>>>> files
>>>>
>>>> --
>>>> 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 new members are moderated - please be patient with
>>>> your first post.
>>>> To unsubscribe from this group, send email to
>>>> clojure+unsubscr...@googlegroups.com
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/clojure?hl=en
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Clojure" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to clojure+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>

Re: 2018 State of Clojure Community Survey is now open!

[Bozhidar Batsov]

What do you mean under "namespace" improvements? (that was one of the areas
we could pick the importance of improvements for) I assumed this means
making the `ns` macro simpler, as I know many people can't use it without
consulting its documentation, but I was curious if it actually meant
something else.

On 25 January 2018 at 17:43, Alex Miller  wrote:

> It's time for the annual State of Clojure Community survey!
>
> If you are a user of Clojure or ClojureScript, we are greatly interested
> in your responses to the following survey:
>
> https://www.surveymonkey.com/r/clojure2018
>
> The survey contains four pages:
>
> 1. General questions applicable to any user of Clojure or ClojureScript
> 2. Questions specific to JVM Clojure (skip if not applicable)
> 3. Questions specific to ClojureScript (skip if not applicable)
> 4. Final comments
>
> The survey will close February 9th. All of the data will be released in
> February. We are greatly appreciative of your input!
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 2018 State of Clojure Community Survey is now open!

[Bozhidar Batsov]

Got it. If I knew all of that I would have given it bigger importance. :-)

I was recently bitten by some issue related to concurrent ns loading (
https://github.com/clojure-emacs/cider/issues/2092#issuecomment-333615901)
I hope that's also on the radar for ns improvements.

On 27 January 2018 at 13:47, Alex Miller  wrote:

> On Sat, Jan 27, 2018 at 2:38 AM, Bozhidar Batsov 
> wrote:
>
>> What do you mean under "namespace" improvements? (that was one of the
>> areas we could pick the importance of improvements for) I assumed this
>> means making the `ns` macro simpler, as I know many people can't use it
>> without consulting its documentation, but I was curious if it actually
>> meant something else.
>>
>
> It is intentionally vague, but it could mean either improvements to ns or
> changes to namespaces themselves. There are some problems around dealing
> with failures during load and performance that I think could be improved by
> immutable namespaces.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] clojure tools 1.9.0.315, tools.deps.alpha 0.5.342

[Bozhidar Batsov]

Well, I might have found one - seems transitive snapshot deps are not
handled properly (at least in the version of tools.deps that's shipped with
Clojure by default:

clj -Sdeps '{:deps {cider/orchard {:mvn/version "0.1.0-SNAPSHOT"}
cider/cider-nrepl {:mvn/version "0.17.0-SNAPSHOT"} }}' -e '(require (quote
cider-nrepl.main)) (cider-nrepl.main/init ["cider.nrepl/cider-middleware"])'

This works, but this doesn't:

clj -Sdeps '{:deps {cider/cider-nrepl {:mvn/version "0.17.0-SNAPSHOT"} }}'
-e '(require (quote cider-nrepl.main)) (cider-nrepl.main/init
["cider.nrepl/cider-middleware"])'

As orchard is a dep of cider-nrepl I find it pretty odd. All non-snapshot
deps seem to be processed normally.



On 24 January 2018 at 19:39, Alex Miller  wrote:

> Let me know if you find any bugs! :)
>
> On Wed, Jan 24, 2018 at 11:18 AM, Bozhidar Batsov 
> wrote:
>
>> That's exactly what I'm planning to do. Thanks for the help, Alex! And
>> thanks for working on this!
>>
>> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] clojure tools 1.9.0.315, tools.deps.alpha 0.5.342

[Bozhidar Batsov]

That's what I get if I don't specify the orchard dep explicitly:

Exception in thread "main" java.io.FileNotFoundException: Could not locate
orchard/misc__init.class or orchard/misc.clj on classpath.,
compiling:(cider/nrepl/middleware/pprint.clj:1:1)

On 27 January 2018 at 20:07, Alex Miller  wrote:

> Can you describe what “not works” looks like? Exception? Wrong dep?
>
> On Jan 27, 2018, at 11:04 AM, Bozhidar Batsov  wrote:
>
> Well, I might have found one - seems transitive snapshot deps are not
> handled properly (at least in the version of tools.deps that's shipped with
> Clojure by default:
>
> clj -Sdeps '{:deps {cider/orchard {:mvn/version "0.1.0-SNAPSHOT"}
> cider/cider-nrepl {:mvn/version "0.17.0-SNAPSHOT"} }}' -e '(require (quote
> cider-nrepl.main)) (cider-nrepl.main/init ["cider.nrepl/cider-
> middleware"])'
>
> This works, but this doesn't:
>
> clj -Sdeps '{:deps {cider/cider-nrepl {:mvn/version "0.17.0-SNAPSHOT"} }}'
> -e '(require (quote cider-nrepl.main)) (cider-nrepl.main/init
> ["cider.nrepl/cider-middleware"])'
>
> As orchard is a dep of cider-nrepl I find it pretty odd. All non-snapshot
> deps seem to be processed normally.
>
>
>
> On 24 January 2018 at 19:39, Alex Miller  wrote:
>
>> Let me know if you find any bugs! :)
>>
>> On Wed, Jan 24, 2018 at 11:18 AM, Bozhidar Batsov 
>> wrote:
>>
>>> That's exactly what I'm planning to do. Thanks for the help, Alex! And
>>> thanks for working on this!
>>>
>>> --
>> 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 new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Clojure" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/clojure/RlHjnJPpFbU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.