[ANN] nREPL 0.6

[Bozhidar Batsov]

Good news, everyone!

We’ve just released nREPL 0.6 and it’s going to rock your REPL world! :-)


It’s a really important release that brings a simplified and more robust
code evaluation model, support for streaming output (that’s extremely
big!), a new way to hook into evaluation errors and many more small tweaks
and improvements. Special thanks to Christophe Grand and Michael Griffiths
who carried out the bulk of the work in this release! You can find the
complete release notes here
https://github.com/nrepl/nrepl/releases/tag/0.6.0 The project’s website
https://nrepl.org will very soon be updated to reflect the new release as
well.


This release is the perfect embodiment of the beautiful OSS idea that when
you’ve got a great community everything is possible. I’ve done 0 work on
this release other that writing this announcement and reviewing a few PRs.
:-) As far as I’m concerned we’re moving in the right direction!

-- 
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] releasing scope-capture-nrepl 0.3.0

[Bozhidar Batsov]

Nice! Thanks for sharing!

I've added it to the list of extensions 
here https://nrepl.org/nrepl/extensions.html

On Sunday, January 6, 2019 at 1:08:50 PM UTC+2, Val Waeselynck wrote:
>
> *scope-capture-nrepl 0.3.0* is out, updates the nREPL dependency to use 
> nrepl/nrepl . Still compatible with 
> the older tools.nrepl .
>
> https://clojars.org/alvalval/scope-capture-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.

Re: [ANN] CIDER 0.19

[Bozhidar Batsov]

Btw, I also wrote a short blog post on the new release
https://metaredux.com/posts/2019/01/01/happy-new-cider.html

On Tue, 1 Jan 2019 at 12:24, Bozhidar Batsov  wrote:

> Hey everyone!
>
> Happy New Year! Live long, live well, have fun and prosper!
>
> To help you start the New Year on the right foot and with the proper mood
> I've just cut CIDER 0.19!
>
> The release notes are here
> https://github.com/clojure-emacs/cider/releases/tag/v0.19.0
>
> The highlights are:
>
> * lots of improvements to the new connection management system
> * some fixes for the changes to the error messages in Clojure 1.10
>
> That's going to be the final CIDER release that will work with the legacy
> tools.nrepl, so if you're a boot or lein user you should definitely upgrade
> to their latest versions which target the modern nREPL.
>
> Cheers!
>

-- 
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.19

[Bozhidar Batsov]

Hey everyone!

Happy New Year! Live long, live well, have fun and prosper!

To help you start the New Year on the right foot and with the proper mood
I've just cut CIDER 0.19!

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

The highlights are:

* lots of improvements to the new connection management system
* some fixes for the changes to the error messages in Clojure 1.10

That's going to be the final CIDER release that will work with the legacy
tools.nrepl, so if you're a boot or lein user you should definitely upgrade
to their latest versions which target the modern nREPL.

Cheers!

-- 
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] rep 0.1.0 - A single-shot nREPL client (hence no 'L')

[Bozhidar Batsov]

Nice to see the first stable release! We should add to the list of known
clients on nrepl.org.

On Thu, 20 Dec 2018 at 00:12, Jason Felice  wrote:

> rep
>
> https://github.com/eraserhd/rep
>
> A single-shot nREPL client designed for shell invocation, to be used as a
> part of editor tooling, scripting, or monitoring.
>
> Binaries are built with Graal VM, so it has super-quick boot and
> turn-around time.  For example, it takes 25ms to execute "(+ 2 2)" in a
> running server.
>
> It connects to a running nREPL server (like kind started with lein repl,
> for example), sends some code to be evaluated, and prints the results and
> output.
>
> $ rep '(clojure.tools.namespace.repl/refresh)'
> :reloading ()
> :ok
>
> --
> 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.10.0-RC1 (please test!)

[Bozhidar Batsov]

You might want to add to the datafy ns and function that they were
introduced in 1.10. I noticed they didn't have the :added metadata that
most Clojure core stuff has (it's very handy in IDEs/starter editors).

On Thu, 11 Oct 2018 at 18:11, Alex Miller  wrote:

> 1.10.0-RC1 is now available. You can try it with clj using:
>
>   clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version
> "1.10.0-RC1"}}}'
>
> 1.10.0-RC1 is the same code as beta2 (only change are some changelog
> fixes).
> You can read the full 1.10 changelog here:
> https://github.com/clojure/clojure/blob/master/changes.md
>
> *Note: This is a release candidate! Please try this release candidate with
> your project and provide feedback (both whether it works as expected and
> any issues).* If there are issues we will assess, otherwise we intend to
> move towards a final release of 1.10.
>
>
> --
> 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.10.0-beta2

[Bozhidar Batsov]

On Wed, 10 Oct 2018 at 16:57, Alex Miller  wrote:

> It's like finding that extra birthday present that got lost under the
> couch. Sorry we added more stuff?
>

I love unexpected gifts! I’m just worried that unexpected problems with the
unexpected gifts might delay the delivery of the expected ones...  It’s
always a bit scary to introduce bigger changes close to release time.


> (copying this from stuff I wrote elsewhere)... Lots of people have built
> things like datafy already in an ad hoc or specialized way, but without the
> benefit of a common shared protocol to do so. If you look inside prn,
> you'll see basically this same kind of thing and prn is an example of
> something that could be rewritten to leverage this facility.
>
> As always, we want to work with data. But there are a lot of complexities
> in dealing with a mixture of Java objects and data, or objects that need to
> be lazily traversed, or data that's coming from external sources, or data
> with cycles in the graphs, etc. datafy has enough hooks via metadata and
> protocols to handle all of those complexities.
>
> If you don't how you would use this, you may not have this kind of a
> problem. There are certainly many people writing this kind of thing already.
>
> On Wednesday, October 10, 2018 at 8:30:48 AM UTC-5, Bozhidar Batsov wrote:
>>
>> My thoughts exactly. :-) Some more information about the new library and
>> the odd timing of its introduction would be appreciated.
>>
>> On Wed, 10 Oct 2018 at 11:19, Herwig Hochleitner 
>> wrote:
>>
>>>
>>> What's datafy and why is it first appearing in a "feature complete"
>>> -beta2 release?
>>>
>>> --
>>> 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.10.0-beta2

[Bozhidar Batsov]

My thoughts exactly. :-) Some more information about the new library and
the odd timing of its introduction would be appreciated.

On Wed, 10 Oct 2018 at 11:19, Herwig Hochleitner 
wrote:

>
> What's datafy and why is it first appearing in a "feature complete" -beta2
> release?
>
> --
> 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.10.0-beta1

[Bozhidar Batsov]

Same here.

On Tue, 9 Oct 2018 at 17:32, Colin Fleming 
wrote:

> I’m not sure a guide is needed for tap - the functions are pretty simple?
>>
>
> Personally, I understand the mechanics, but I have no idea how they're
> intended to be used. I'd love to see some examples of what they're designed
> to do.
>
> On Sat, 6 Oct 2018 at 12:17, Alex Miller  wrote:
>
>>
>> > On Oct 6, 2018, at 3:53 AM, Mike <145...@gmail.com> wrote:
>> >
>> > Cool! Will there be more guides how to use tap and prepl ?
>>
>> I’m not sure a guide is needed for tap - the functions are pretty simple?
>> I’ll think about it.
>>
>> prepl is designed for tool makers so is probably a limited audience and
>> not really a good target for a guide. The docstrings have a lot more detail
>> and may lead to some updated reference material.
>>
>> > Is there any plans to release  clj for windows?
>>
>> Yes, but I can’t give you a timeframe. Significant work has been 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.
>>
> --
> 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.18 (Saigon) is out!

[Bozhidar Batsov]

Hey everyone,

Just wanted to let you know I've just released CIDER 0.18 (Saigon)! It's a
massive release with a TON of changes and improvements and a MAJOR step on
the road to CIDER 1.0! Here are some of the highlights:

New features

   - #2375 : Move
   cider-eval-toplevel-inside-comment-form into clojure-mode as
   clojure-toplevel-inside-comment-form so beginning-of-defun is aware of
   comment forms.
   - Add new cider-session-name-template variable for flexible
   customization of cider session and REPL buffer names.
   - Bind C-c M-r to cider-restart.
   - Add new cider-start-map keymap (C-c C-x) for jack-in and connection
   commands.
   - Add new cider-ns-map keymap (C-c M-n) for namespace related
   functionality.
   - Allow evaling top level forms in a comment form rather than the entire
   comment form with cider-eval-toplevel-inside-comment-form.
   - Create keymap for inserting forms into the repl at C-c C-j.
   - Add new defcustom cider-invert-insert-eval-p: Set to cause
   insert-to-repl commands to eval the forms by default when inserted.
   - Add new defcustom cider-switch-to-repl-after-insert-p: Set to prevent
   cursor from going to the repl when inserting a form in the repl with the
   insert-to-repl commands.
   - Inject piggieback automatically on cider-jack-in-clojurescript.
   - Introduce a new command named cider (C-c M-x) that acts as a simple
   wrapper around all commands for starting/connecting to REPLs.
   - #2305 : Make it
   possible to disable the REPL type auto-detection by customizing
   cider-repl-auto-detect-type.
   - #2373 : Make it
   possible to configure the welcome message displayed in scratch buffers via
   cider-scratch-initial-message.
   - Add the ability to jump to the profiler buffer using cider-selector.
   - #1980 : Echo back
   missing namespace name on interactive eval (requires nREPL 0.4.3+).
   - #2397 : Add
   shadow-select CLJS REPL type.
   - #2314 : Add
   cider-ns-reload and cider-ns-reload-all interactive commands.

Bugs fixed

   - #2317 : The stdin
   prompt can now be cancelled.
   - #2328 : Added
   cider-eval-sexp-to-point.
   - #2310 :
   cider-format-edn-last-sexp will format the last sexp.
   - #2294 : Fix
   setting default stacktrace filters.
   - #2286 : Fix eldoc
   issue with images in the REPL.
   - #2307 : Use a better
   error when a cljs repl form cannot be found.
   - Fix the broken test selector functionality.
   - #2291 :
   cider-use-tooltips custom variable works as expected.
   - #2424 : Fallback
   to lein as the default jack-in command when clojure is not present.

Changes

   - (Breaking) Move cider-repl-set-ns, previously on C-c M-n, on C-c M-n
   (M-)n in the cider-ns-map.
   - (Breaking) Move cider-ns-refresh, previously on C-c C-x, on C-c M-n
   (M-)r in the cider-ns-map.
   - (Breaking) Bump the minimum required Emacs version to 25.1.
   - (Breaking) Drop support for Java 7 and Clojure(Script) 1.7.
   - (Breaking) Use session name as part of CIDER buffers names (REPL,
   server, messages), and obsolete nrepl-buffer-name-separator and
   nrepl-buffer-name-show-port. See cider-session-name-template and
   cider-format-connection-params for how to customize CIDER buffer names.
   - Rename cider-eval-defun-to-point to cider-eval-defun-up-to-point.
   - Add support for printing to the current buffer to
   cider-eval-defun-up-to-point.
   - Remove cider-ping command.
   - Remove cider-visit-error-buffer in favour of using cider-selector.
   - Rename cider-refresh to cider-ns-refresh (and all the related
   defcustoms).
   - (Breaking) Rewrote connection management (see
   http://docs.cider.mx/en/latest/managing_connections/ for details).
   - (Breaking) cider-jack-in-clojurescript now creates only a
   ClojureScript REPL (use cider-jack-in-clj to create both REPLs).
   - #2357 : Support
   both keywords and strings as test selectors (previously it was only
   strings).
   - #2378 : Add
   autoloads target to Makefile.
   - Map cider-pprint-eval-last-sexp to C-c C-v (C-)f (C-)e in the
   cider-eval-commands-map.
   - Map cider-pprint-eval-defun-at-point to C-c C-v (C-)f (C-)d in the
   cider-eval-commands-map.
  

[ANN] nREPL 0.4.5 released!

[Bozhidar Batsov]

Hey everyone!

Just wanted to let you know that a new version of nREPL was released today.
Here's the list of (small) changes and improvements:

New features

   - The built-in the CLI generates an .nrepl-port file on server startup.
   - #39 : Add a --connect
command-line
   option allowing you to connect.
   with the built-in client to an already running nREPL server.
   - Add shorthand names for most command-line options.
   - Add a -v/--version command-line option.

Changes

   - #32 : Extract the bencode
   logic in a separate library .

Bugs fixed

   - #38 : Remove extra newline
   in REPL output.


It's probably easy to figure out that most of the changes were done to
improve the user experience for clojure-cli-tools users (aka clj).

Enjoy!

-- 
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] nREPL 0.4.4 released with improved support for clj

[Bozhidar Batsov]

Hey everyone,

nREPL 0.4.4 is out with a few improvements to its command-line interface.

New features

   - Added --help command-line option.
   - Added --bind command-line option.
   - Added --handler and --middleware command-line options. Extremely
   useful when starting nREPL using
   clj and tools.deps, as this allows you to inject middleware trivially
   without the need for
   something like lein or boot.

See http://nrepl.readthedocs.io/en/latest/usage/ for more details on how to
load 3rd-party middleware using --middleware.
Bugs fixed

   - Add missing newline after colorized values displayed in the REPL.


Very simply put - now you can load whatever middleware you want as simple
as running something like (provided you've setup this alias as explained in
the manual, that is):

clj -R:nREPL -m nrepl.cmdline --middleware "[cider.piggieback/wrap-cljs-repl]"


Enjoy!

-- 
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.17 (Andalucía) is out!

[Bozhidar Batsov]

On 7 May 2018 at 23:07, Gregg Reynolds <d...@mobileink.com> wrote:

> Looks awesome!
>
> Any idea when 1.0 will be out?
>

Not really. Most likely when the internal improvements section of the
roadmap is completed
https://github.com/clojure-emacs/cider/blob/master/ROADMAP.md, but work is
progressing slowly.


>
> On Mon, May 7, 2018, 2:55 PM Bozhidar Batsov <bozhi...@batsov.com> wrote:
>
>> Hey everyone!
>>
>> I'm happy to share with you that CIDER finally made it all the way
>> to Andalucía! This was a massive release that added a lot of new
>> functionality and improved much of the existing one. Here are the most
>> important changes in a nutshell:
>>
>> - improved ClojureScript support
>> - the ability to display images in the REPL
>> - support for deps.edn "projects"
>> - support for test selectors
>> - much of the core functionality on the Clojure side was been extracted
>> to a stand-alone library https://github.com/clojure-emacs/orchard
>> (that's step towards socket REPL support and stronger cross-editor
>> collaboration)
>>
>> And here are all the details:
>>
>> ### New features
>>
>> * [#2248](https://github.com/clojure-emacs/cider/pull/2248):
>> `cider-repl` can now display recognized images in the REPL buffer.
>> * [#2172](https://github.com/clojure-emacs/cider/pull/2172): Render
>> diffs for expected / actual test results.
>> * [#2167](https://github.com/clojure-emacs/cider/pull/2167): Add new
>> defcustom `cider-jdk-src-paths`. Configure it to connect stack trace links
>> to Java source code.
>> * [#2161](https://github.com/clojure-emacs/cider/issues/2161): Add new
>> interactive command `cider-eval-defun-to-point` which is bound to `C-c C-v
>> (C-)z`. It evaluates the current top-level form up to the point.
>> * [#2113](https://github.com/clojure-emacs/cider/issues/2113): Add new
>> interactive commands `cider-eval-last-sexp-in-context` (bound to `C-c
>> C-v (C-)c`) and `cider-eval-sexp-at-point-in-context` (bound to `C-c C-v
>> (C-)b`).
>> * Add new interactive command `cider-repl-set-type`.
>> * [#1976](https://github.com/clojure-emacs/cider/issues/1976): Add new
>> interactive command `cider-connect-clojurescript`.
>> * Add a menu for `cider-browse-ns-mode`.
>> * [#2160](https://github.com/clojure-emacs/cider/issues/2160): Make it
>> possible to configure the default `*print-level*` and `*print-length*` via
>> defcustoms (`cider-repl-print-level` and `cider-repl-print-length`).
>> * New interactive command `cider-cheatsheet` allows you to browse the
>> Clojure Cheatsheet with an Emacs interface.
>> * [#2191](https://github.com/clojure-emacs/cider/issues/2191): Add
>> support for jacking-in just with the `clojure` command-line tool and
>> `tools.deps`.
>> * Make it possible to start a Nashorn ClojureScript REPL.
>> * [#2235](https://github.com/clojure-emacs/cider/pull/2235): Make the
>> REPL ignore blank input rather than evaluating.
>> * [#2241](https://github.com/clojure-emacs/cider/pull/2241): Make
>> `cider-test-ediff` diff eval'ed values.
>> * Add support for shadow-cljs to `cider-jack-in`.
>> * [#2244](https://github.com/clojure-emacs/cider/issues/2244): Display
>> the REPL type in the modeline.
>> * [#2238](https://github.com/clojure-emacs/cider/pull/2238): Allow
>> specifying predicates for entries in `cider-jack-in-lein-plugins` and
>> `cider-jack-in-nrepl-middlewares`.
>> * Add support for test selectors. If test all or all loaded is called
>> with a prefix ask for filter test selectors in the minibuffer and only run
>> those tests in the project which match the filters. Add variation of test
>> namespace which asks for filter selectors the same way and only runs a
>> subset of the namespace tests.
>> * Add a configuration variable allowing to control whether server output
>> should be redirected to the REPL (`cider-redirect-server-
>> output-to-repl`).
>>
>> ### Bugs Fixed
>>
>> * [#1913](https://github.com/clojure-emacs/cider/issues/1913): Fix
>> `cider-toggle-buffer-connection` to allow cycling of connection and
>> restoring all connections in cljc buffers.
>> * [#2148](https://github.com/clojure-emacs/cider/issues/2148): Fix `jump
>> to definition` working properly when remote `cider-jack-in` and
>> `cider-connect`.
>> * Font-lock failed assertions even in tests that were evaluated
>> interactively.
>> * [#2102](https://github.com/clojure-emacs/cider/issues/2102): Make
>> `cider-format-buffer` handle mismatched parens gracefully.
>>
>> ### Changes
>>
>

[ANN] CIDER 0.17 (Andalucía) is out!

[Bozhidar Batsov]

Hey everyone!

I'm happy to share with you that CIDER finally made it all the way
to Andalucía! This was a massive release that added a lot of new
functionality and improved much of the existing one. Here are the most
important changes in a nutshell:

- improved ClojureScript support
- the ability to display images in the REPL
- support for deps.edn "projects"
- support for test selectors
- much of the core functionality on the Clojure side was been extracted to
a stand-alone library https://github.com/clojure-emacs/orchard (that's step
towards socket REPL support and stronger cross-editor collaboration)

And here are all the details:

### New features

* [#2248](https://github.com/clojure-emacs/cider/pull/2248): `cider-repl`
can now display recognized images in the REPL buffer.
* [#2172](https://github.com/clojure-emacs/cider/pull/2172): Render diffs
for expected / actual test results.
* [#2167](https://github.com/clojure-emacs/cider/pull/2167): Add new
defcustom `cider-jdk-src-paths`. Configure it to connect stack trace links
to Java source code.
* [#2161](https://github.com/clojure-emacs/cider/issues/2161): Add new
interactive command `cider-eval-defun-to-point` which is bound to `C-c C-v
(C-)z`. It evaluates the current top-level form up to the point.
* [#2113](https://github.com/clojure-emacs/cider/issues/2113): Add new
interactive commands `cider-eval-last-sexp-in-context` (bound to `C-c C-v
(C-)c`) and `cider-eval-sexp-at-point-in-context` (bound to `C-c C-v
(C-)b`).
* Add new interactive command `cider-repl-set-type`.
* [#1976](https://github.com/clojure-emacs/cider/issues/1976): Add new
interactive command `cider-connect-clojurescript`.
* Add a menu for `cider-browse-ns-mode`.
* [#2160](https://github.com/clojure-emacs/cider/issues/2160): Make it
possible to configure the default `*print-level*` and `*print-length*` via
defcustoms (`cider-repl-print-level` and `cider-repl-print-length`).
* New interactive command `cider-cheatsheet` allows you to browse the
Clojure Cheatsheet with an Emacs interface.
* [#2191](https://github.com/clojure-emacs/cider/issues/2191): Add support
for jacking-in just with the `clojure` command-line tool and `tools.deps`.
* Make it possible to start a Nashorn ClojureScript REPL.
* [#2235](https://github.com/clojure-emacs/cider/pull/2235): Make the REPL
ignore blank input rather than evaluating.
* [#2241](https://github.com/clojure-emacs/cider/pull/2241): Make
`cider-test-ediff` diff eval'ed values.
* Add support for shadow-cljs to `cider-jack-in`.
* [#2244](https://github.com/clojure-emacs/cider/issues/2244): Display the
REPL type in the modeline.
* [#2238](https://github.com/clojure-emacs/cider/pull/2238): Allow
specifying predicates for entries in `cider-jack-in-lein-plugins` and
`cider-jack-in-nrepl-middlewares`.
* Add support for test selectors. If test all or all loaded is called with
a prefix ask for filter test selectors in the minibuffer and only run those
tests in the project which match the filters. Add variation of test
namespace which asks for filter selectors the same way and only runs a
subset of the namespace tests.
* Add a configuration variable allowing to control whether server output
should be redirected to the REPL (`cider-redirect-server-output-to-repl`).

### Bugs Fixed

* [#1913](https://github.com/clojure-emacs/cider/issues/1913): Fix
`cider-toggle-buffer-connection` to allow cycling of connection and
restoring all connections in cljc buffers.
* [#2148](https://github.com/clojure-emacs/cider/issues/2148): Fix `jump to
definition` working properly when remote `cider-jack-in` and
`cider-connect`.
* Font-lock failed assertions even in tests that were evaluated
interactively.
* [#2102](https://github.com/clojure-emacs/cider/issues/2102): Make
`cider-format-buffer` handle mismatched parens gracefully.

### Changes

* [#2163](https://github.com/clojure-emacs/cider/issues/2163): Add
`cider-browse-spec-regex`, and changed `cider-browse-spec-all` to use it.
* [#2029](https://github.com/clojure-emacs/cider/pull/2154): Make cider-doc
use cider-browse-spec functionality to print the spec part of the doc buffer
* [#2151](https://github.com/clojure-emacs/cider/pull/2151): Improve
formatting of spec in `cider-doc` buffer.
* Remove support for CLJX.
* Fix `cider-eval-region` masking `clojure-refactor-map` in
`cider-repl-mode`.
* [#2171](https://github.com/clojure-emacs/cider/issues/2171): Update `See
Also` mappings for Clojure 1.9.
* [#2202](https://github.com/clojure-emacs/cider/issues/2202): Make
`cider-jack-in-clojurescript` prompt from the ClojureScript REPL type to
use.
* [#2202](https://github.com/clojure-emacs/cider/issues/2202): Don't try to
start a ClojureScript REPL before checking whether that's possible or not.
* [orchard#24](https://github.com/clojure-emacs/orchard/pull/24): Inspector
now separately renders clickable keys and values when inspecting maps.
* [orchard#24](https://github.com/clojure-emacs/orchard/pull/24): Inspector
now remembers the 

Re: [ANN] [org.clojure/java.classpath "0.3.0"] with Java 9 support

[Bozhidar Batsov]

Thanks!

On 6 May 2018 at 21:02, Stuart Sierra  wrote:

> https://github.com/clojure/java.classpath - utility functions to
> search the Java classpath.
>
> Build #339  is
> complete, should be sync'd with the
> Maven Central repository soon.
>
> Release 0.3.0:
>
> * Fix [CLASSPATH-8 ]:
> empty classpath returned on Java 9.
>
> Starting with Java 9, the default class loader is no longer an
> instance of URLClassLoader, so `classpath` returned an empty sequence.
> The strategy of using URLClassLoader started with release [0.2.0] to
> accommodate Java application containers (see [CLASSPATH-1]
>  and
> [CLASSPATH-2 ]). After
> this change, application containers based on
> URLClassLoader should still work as expected.
>
> On Java 9 without an application container, it appears that the
> `java.class.path` system property is the only way to get the
> classpath. While this is essentially a bugfix for Java 9
> compatibility, it is a change in behavior, hence the version change
> from 0.2 to 0.3.
>
> Leiningen dependency information:
>
> [org.clojure/java.classpath "0.3.0"]
>
> Maven dependency information:
>
> 
>   org.clojure
>   java.classpath
>   0.3.0
> 
>
> Gradle dependency information:
>
> compile "org.clojure:java.classpath:0.3.0"
>
>
> --
> 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: Why does interruptible-eval from tools.nrepl queue evaluations?

[Bozhidar Batsov]

By channel you mean sessions right? That's a simple way to circumvent the
serialized nature of evaluations - you can just spin a new session for each
evaluation. Never benchmarked what's the overhead of this, though.

On 4 May 2018 at 00:36, Gary Fredericks  wrote:

> I used the hacky tactic of just sending messages through the nrepl
> channels (while the eval is blocked) to implement this:
> https://github.com/gfredericks/debug-repl
>
> Gary Fredericks
> (803)-295-0195
> fredericksg...@gmail.com
> gfredericks.com
>
> On Thu, May 3, 2018 at 4:31 PM, Carlo Zancanaro 
> wrote:
>
>>
>> On Thu, May 03 2018, Gary Fredericks wrote:
>>
>>> Separately, I use this macro >> s/repl-utils#bg> for running background things in the repl. It probably
>>> targets different concerns, but seems related at least.
>>>
>>
>> My use case is quite different. Requiring someone to decide ahead of time
>> to run code in the background (ie. by wrapping it in another form) won't
>> work for me at all.
>>
>> I'm trying to write a Common Lisp interactive restart system, somewhat
>> similar to what Slime gives you. It actually works pretty well, but it's
>> often helpful to be able to redefine things, or to run some code to change
>> a data structure, before selecting a restart. While waiting for a restart
>> selection the eval thread is blocked, though, so other evaluations have to
>> happen in another thread. The nrepl protocol seems like it was designed for
>> this, given how asynchronous it is, so I was surprised that
>> interruptible-eval explicitly queued up evaluations and ran them
>> sequentially.
>>
>> I've ended up doing this as a solution: https://github.com/czan/dont-g
>> ive-up.nrepl/blob/acc20e0c25aa90a5c991b9cd1f7cc4abe2f1cd6b/s
>> rc/dont_give_up/nrepl.clj#L335. This isn't perfect. There are further
>> modifications required to be able to interrupt evaluations other than the
>> most recent one, but it works well enough to be useful. If anyone has a
>> reason why this is a terrible idea, I'm all ears.
>>
>> Carlo
>>
>
> --
> 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: Developing in Clojure with Emacs: Mastering the Keyboard

[Bozhidar Batsov]

Btw, didn't you find the instructions in the official manual useful (
http://cider.readthedocs.io/en/latest/installation/ and
http://cider.readthedocs.io/en/latest/up_and_running/). Admitted they are
not great, but they do cover a lot of ground and are reasonably up-to-date.

On 3 March 2018 at 23:11, Chris Shellenbarger  wrote:

> I spent the last week learning and using Emacs and CIDER for Clojure
> Development.
>
> I've started to write up a lot of the lessons I've learned from doing so
> in the hopes that it will help some other people who attempt something
> similar.
>
> Anyway, if you're interested in getting started with Emacs and CIDER,
> you'll have to learn about how to use the keyboard so I wrote a couple of
> key lessons in a Medium post:  Developing in Clojure with Emacs:
> Mastering the Keyboard
> 
> .
>
> My environment was Emacs 24.5.1 with CIDER 0.16.0 on Linux Mint 18.3.
>
> I used the Clojure for the Brave and True  book
> for a basic intro into Emacs  and
> used the provided emacs configuration files as a starting point.  However,
> these only worked with CIDER 0.8.0 and were about four years old.  I made
> some modifications of the files to work with CIDER 0.16.0 and put them up
> for anyone to use on my BitBucket Repository
> .
>
> I have a lot more to share about my Emacs experience, but I found that
> there was so much that I had to split it into multiple posts.
>
> Hope it helps someone out there!
>
>
>
> --
> 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: Why does the `def-` not exist?

[Bozhidar Batsov]

> We're not going to add def-. There is regret over even adding defn-, but
we don't take things away...

Well, that's not really necessary. Why not just mark it deprecated and keep
it around forever. That's the Java approach and I think it's pretty
reasonable and close to what you aim for. Nothing really gets broken, but
you get to nudge people away from using certain problematic APIs. That
would also wrap once and for all recurring discussions like this one.

I think Clojure's principle of ensuring backwards compatibility is awesome,
but I also think there's little harm in deprecating things from time to
time. This sends a very strong message to users about the preferred ways of
writing in Clojure.

On 28 February 2018 at 05:33, Alex Miller  wrote:

>
> On Tuesday, February 27, 2018 at 1:13:52 PM UTC-6, Leon Grapenthin wrote:
>>
>> I'm sure you'd all use def- if it existed. Even if you could just type
>> the much simplified ^:private, use an editor snippet, refer your own macro,
>> or create a whole new namespace for it. You'd do none of that. You'd
>> totally fall for the trap and type def-, the syntactic aid that should not
>> be there.
>>
>
> I'm sure I would. But I don't need it. If it was there, we'd be having the
> same discussion about defmacro- or defmulti- or whatever. There has to be a
> line somewhere, we drew before def-.
>
>
>> There is "regret over even adding defn-"? You used defn- just recently in
>> the tools.deps.alpha core namespace 9 times. Rich used it in clojure.spec
>> core namespace 46 times. :)))
>>
>
> Sure, it's there. But if it wasn't, I'd use ^:private and never worry
> about it.
>
>
>> Jokes aside, if Rich simply doesn't want it that's fine of course - it's
>> his language. However if people ask me again I will just say that instead.
>> Believe it or not, I got this question three times last year and the "copy
>> N things" argument failed 3/3.
>>
>
> Why even make the argument? If you want def- in your code, then add it.
> It's a Lisp - we can all have the language we want.
>
> The impl ns pattern recommended by Timothy is truly a very good one that I
>> apply a lot myself, especially in larger projects and when "private" macro
>> helpers are involved (and probably the only solid workaround recommended
>> here because it has value in itself).
>>
>
> I use this one as well (I haven't doc'ed it all yet because I'm still
> fighting with autodoc) but I consider parts of tools.deps.alpha public and
> parts to be "impl".
>
>
>> How much do I def things? - I haven't done the computation but I'm pretty
>> sure that I def more things ^:private than I def things public. Little
>> lookup tables etc.. Also I'd argue that def is the second most used top
>> level form after defn. If not, the ones that come before don't have
>> ^:private semantics. Well, if there was any chance for def- left I'd do a
>> statistic over available codebases - let me know.
>>
>
> Here's a quick and dirty stat based on the set of ~375 projects I have at
> hand:
>
> [~/code]$ ack -c -h --clojure "\(defn- " */src
> 5106
> [~/code]$ ack -c -h --clojure "\(defn " */src
> 14344
> [~/code]$ ack -c -h --clojure "\(def " */src
> 3924
> [~/code]$ ack -c -h --clojure "\(def \^:private" */src
> 559   # note this is a subset of prior, first pair are
> disjoint
>
> defn is 5x more common than def. About 14% of def's are private and 26% of
> defns are private. On average I have <2 private defs per project. That
> doesn't do much to convince me it's a priority.
>
> --
> 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]

My bad. Actually we shouldn't need the deps at all as they're supposed to
be inlined in the artefact even now. No idea what exactly's going on here,
but I guess we'll sort it out with Benedek.

On 29 January 2018 at 11:38, Bozhidar Batsov <bozhi...@batsov.com> wrote:

> Ah, yeah - that's an odd situation that I didn't think about. I guess with
> clj we'll have to enumerate all the deps explicitly, although this would
> make the code vulnerable to dependency conflicts (the reason why we're
> doing this source rewriting to begin with).
>
> On 28 January 2018 at 05:38, Alex Miller <a...@puredanger.com> wrote:
>
>> clj uses the dependencies for the published Maven artifact. The published
>> artifact has a pom with dependencies only on clojure and tools.nrepl, so
>> orchard is not a dependency that is found or can be traversed. Here's an
>> example snapshot pom in clojars, which is what any Maven user of this
>> artifact will see:
>>
>> https://clojars.org/repo/cider/cider-nrepl/0.17.0-SNAPSHOT/
>> cider-nrepl-0.17.0-20180123.225352-7.pom
>>
>> It seems that this is related to the use of the mranderson source-deps
>> plugin. The orchard dependency is renamed and included as part of the cider
>> source rather than depending on the actual namespaces. Thus, the
>> cider-nrepl artifact actually contains the orchard namespaces already, but
>> under a name like cider.inlined-deps.orchard.v0v
>> 1v0-20180123v122522-8.orchard.misc (note that this is snapshot version
>> specific).
>>
>> So, this looks like clj is doing what is expected given the setup for
>> cider-nrepl.
>>
>>
>> On Sat, Jan 27, 2018 at 9:05 PM, Bozhidar Batsov <bozhi...@batsov.com>
>> wrote:
>>
>>> 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 <a...@puredanger.com> wrote:
>>>
>>>> Can you describe what “not works” looks like? Exception? Wrong dep?
>>>>
>>>> On Jan 27, 2018, at 11:04 AM, Bozhidar Batsov <bozhi...@batsov.com>
>>>> 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 <a...@puredanger.com> wrote:
>>>>
>>>>> Let me know if you find any bugs! :)
>>>>>
>>>>> On Wed, Jan 24, 2018 at 11:18 AM, Bozhidar Batsov <bozhi...@batsov.com
>>>>> > 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 gr

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

[Bozhidar Batsov]

Ah, yeah - that's an odd situation that I didn't think about. I guess with
clj we'll have to enumerate all the deps explicitly, although this would
make the code vulnerable to dependency conflicts (the reason why we're
doing this source rewriting to begin with).

On 28 January 2018 at 05:38, Alex Miller <a...@puredanger.com> wrote:

> clj uses the dependencies for the published Maven artifact. The published
> artifact has a pom with dependencies only on clojure and tools.nrepl, so
> orchard is not a dependency that is found or can be traversed. Here's an
> example snapshot pom in clojars, which is what any Maven user of this
> artifact will see:
>
> https://clojars.org/repo/cider/cider-nrepl/0.17.0-
> SNAPSHOT/cider-nrepl-0.17.0-20180123.225352-7.pom
>
> It seems that this is related to the use of the mranderson source-deps
> plugin. The orchard dependency is renamed and included as part of the cider
> source rather than depending on the actual namespaces. Thus, the
> cider-nrepl artifact actually contains the orchard namespaces already, but
> under a name like 
> cider.inlined-deps.orchard.v0v1v0-20180123v122522-8.orchard.misc
> (note that this is snapshot version specific).
>
> So, this looks like clj is doing what is expected given the setup for
> cider-nrepl.
>
>
> On Sat, Jan 27, 2018 at 9:05 PM, Bozhidar Batsov <bozhi...@batsov.com>
> wrote:
>
>> 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 <a...@puredanger.com> wrote:
>>
>>> Can you describe what “not works” looks like? Exception? Wrong dep?
>>>
>>> On Jan 27, 2018, at 11:04 AM, Bozhidar Batsov <bozhi...@batsov.com>
>>> 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 <a...@puredanger.com> wrote:
>>>
>>>> Let me know if you find any bugs! :)
>>>>
>>>> On Wed, Jan 24, 2018 at 11:18 AM, Bozhidar Batsov <bozhi...@batsov.com>
>>>> 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...

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 <a...@puredanger.com> wrote:

> Can you describe what “not works” looks like? Exception? Wrong dep?
>
> On Jan 27, 2018, at 11:04 AM, Bozhidar Batsov <bozhi...@batsov.com> 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 <a...@puredanger.com> wrote:
>
>> Let me know if you find any bugs! :)
>>
>> On Wed, Jan 24, 2018 at 11:18 AM, Bozhidar Batsov <bozhi...@batsov.com>
>> 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.

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 <a...@puredanger.com> wrote:

> Let me know if you find any bugs! :)
>
> On Wed, Jan 24, 2018 at 11:18 AM, Bozhidar Batsov <bozhi...@batsov.com>
> 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: 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 <a...@puredanger.com> wrote:

> On Sat, Jan 27, 2018 at 2:38 AM, Bozhidar Batsov <bozhi...@batsov.com>
> 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: 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: [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 <a...@puredanger.com> 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 <bozhi...@batsov.com>
> 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 <a...@puredanger.com> 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 <bozhi...@batsov.com>
>>> 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 <a...@puredanger.com> 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.
>>>>

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 <a...@puredanger.com> 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 <bozhi...@batsov.com> 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 <a...@puredanger.com> 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 g

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: 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: 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.

[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: 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 ( 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.

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 

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: 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, 

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 

[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`).
* 

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.

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.

[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: [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.

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=state%3Aopen+label%
> 3Ahacktoberfest=advsearch=Issues=%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: 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 <bozhi...@batsov.com> wrote:

> A long time ago this function was renamed to cider-current-connection.
>
> On 30 September 2016 at 00:56, <fah...@gmail.com> 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"
>&g

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 

[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 

Re: CCW stopped working. How do I fix it?

[Bozhidar Batsov]

On 4 May 2016 at 05:46, Fluid Dynamics  wrote:

> On Wednesday, May 4, 2016 at 7:12:35 AM UTC-4, Miguel Ping wrote:
>>
>> Seems like you need to update eclipse? I'm guessing Marketplace Client is
>> from eclipse.
>>
>
> It's the standalone CCW. But I tried to update all of the components
> listed as inside it, including the Eclipse based ones. I'm fairly sure it's
> looking for this dependency *on the net* and not finding it.
>
> Is there any other workaround for the timeout problem than updating CCW
> (or downgrading Java back to J7something, which is a security risk)?
>
>
>> I recommedn using either cursive or emacs anyway :D
>>
>
> Doesn't cursive (or its host) cost money and emacs cost gray hairs?
>

I find such remarks to be distasteful. Emacs is very user-friendly, but
it's pretty picky about its friends...

Anyways, I don't think this mailing list is the place to report
tool-specific bugs in the first place.


> Not to mention, I have a large preexisting project in this CCW instance
> (the very one I'm hoping to revive from dormancy) and would have to futz
> around with TWO manuals for IDEs to figure out how to export it from one
> and import it into the other.
>
> Also, nothing you wrote addresses the other complaint I have, which is
> that stuff shouldn't just magically stop working one day while it's sitting
> in a drawer unused, and that there's not even an *excuse* for it to do so
> if it's *software*.
>
> --
> 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 test - Print to Report?

[Bozhidar Batsov]

Can you be a bit more specific? What do you mean by "report results"?

On 2 May 2016 at 20:29, JvJ  wrote:

> I've been using cider test, and I think it's great.
>
> However, I would like to know if it's possible to report results so that
> they appear in cider's automatically-generated test report.
>
> Does anyone know if this is possible?
>
> 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] CIDER 0.12 (Seattle)

[Bozhidar Batsov]

On 18 April 2016 at 03:22, Leon Grapenthin <grapenthinl...@gmail.com> wrote:

> Is there still a one page version of the manual so that I can use full
> text search like on the old README?
>

Nope, there's not a single page version of the manual anymore.



> Asking beacuse the readthedocs search function returns 0 results for
> "shortcut" or "shortcuts".
>

That's a known bug in readthedocs when using mkdocs to generate the docs.
Eventually we'll either switch to sphinx or change the manual's hosting.
Unfortunately I don't have time to deal with this right now. As a
workaround you can grep in the markdown code of the manual.


>
> Besides thank you very much.
>


>
> On Sunday, April 17, 2016 at 4:54:44 AM UTC+2, Bozhidar Batsov wrote:
>>
>> Hey everyone,
>>
>> CIDER 0.12 (Seattle) is out! It packs a lot of small improvements and bug
>> fixes!
>>
>> Check out the release notes here
>> https://github.com/clojure-emacs/cider/releases/tag/v0.12.0
>>
>> We've also got a brand new user manual
>> http://cider.readthedocs.org/en/stable/ for your
>> consideration. We'd love to get some help and feedback to make it better.
>>
>> Enjoy!
>>
>

-- 
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.12 (Seattle)

[Bozhidar Batsov]

Hey everyone,

CIDER 0.12 (Seattle) is out! It packs a lot of small improvements and bug
fixes!

Check out the release notes here
https://github.com/clojure-emacs/cider/releases/tag/v0.12.0

We've also got a brand new user manual
http://cider.readthedocs.org/en/stable/ for your
consideration. We'd love to get some help and feedback to make it better.

Enjoy!

-- 
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: Symbol's function definition is void: cider-turn-on-eldoc-mode

[Bozhidar Batsov]

This was deprecated a while back (and deleted recently). Use `eldoc-mode`
instead in your hooks.

On 16 April 2016 at 08:55, Johannes  wrote:

> Hi every,
>
> I have upgrade the latest emacs-cider:
> clojure-mode (version 5.3.0)
> CIDER 0.12.0snapshot (package: 20160414.1712)
>
> But now when I try to start a nREPL server I get the following error
> messages:
>
> nREPL server started on 64355
> [nREPL] Establishing direct connection to localhost:64355 ...
> [nREPL] Direct connection established
> error in process filter: run-hooks: Symbol's function definition is void:
> cider-turn-on-eldoc-mode
> error in process filter: Symbol's function definition is void:
> cider-turn-on-eldoc-mode
>
> I never saw this message before. What ist going wrong?
>
> Johannes
>
> --
> 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] Elements of Clojure

[Bozhidar Batsov]

Seems to me that some more Clojure-specific naming rules can be
incorporated into the first chapter (e.g. like the ones we have here
https://github.com/bbatsov/clojure-style-guide/#naming). Other than this
small remark - excellent work!

On 19 March 2016 at 13:20, Val Waeselynck  wrote:

> The chapter on naming is brilliant, I rarely learned so much in so few
> pages :)
>
> So far I have found the content to be more about 'philosophical'
> programming notions than Clojure specifically, but the parts about Clojure
> are useful and pratical.
>
> You may want to state more explicitly how this books positions itself
> relative to others.
>
> Looking forward to the rest,
>
> Val
>
>
> On Thursday, 17 March 2016 18:47:55 UTC+1, Zach Tellman wrote:
>>
>> I'm writing a book about Clojure, aimed at people who already know the
>> core concepts, and want to use them more effectively.  The first chapter,
>> "Names", is complete and can be read for free.  Details can be found at
>> http://elementsofclojure.com/.
>>
>> I'm happy to answer any questions here, or on the book's mailing list at
>> https://groups.google.com/forum/#!forum/elements-of-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.

[ANN] CIDER 0.11 Released!

[Bozhidar Batsov]

Hey everyone,

CIDER 0.11 (a.k.a. Bulgaria) is finally out!

Today Bulgarians (like me) celebrate the country's Liberation Day and the
rest of the
world will get to celebrate the release of CIDER 0.11. :-)

Once again we've got a ton of new features, refinements and bugfixes and I
hope you're going to love them!

The changelog is here
https://github.com/clojure-emacs/cider/releases/tag/v0.11.0

Enjoy!

-- 
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: Is there a clojure equivalent of ghc-mod? If not, what are the challenges?

[Bozhidar Batsov]

They use the same backend, btw -
https://github.com/clojure-emacs/cider-nrepl

On 28 February 2016 at 01:14, David Della Costa 
wrote:

> Are you looking for something like CIDER,
>
> https://github.com/clojure-emacs/cider
>
> or maybe fireplace?
>
> https://github.com/tpope/vim-fireplace
>
> Think both those projects' READMEs describe current gotchas/bugs/etc.
>
>
> 2016-02-26 21:45 GMT-05:00 Sam DeSota :
>
>>
>> I'm getting to know Clojure and lisps in general and am having a great
>> time. I've worked with Haskell before, and using ghc-mod with various tools
>> was massively useful. Is there a similar tool for Clojure, and what are the
>> challenges if not?
>>
>> --
>> 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: [ldnclj] Re: Suggestions for open source contributions?

[Bozhidar Batsov]

If you're into tooling - there's always plenty of work to be done on
cider-nrepl (https://github.com/clojure-emacs/cider-nrepl) :-)

On 2 February 2016 at 10:28, Chris Howe-Jones 
wrote:

> Another open source library that has some real momentum behind it at the
> moment is baid-chat https://github.com/braidchat/meta/wiki . It's the
> Clojure Communities OSS alternative to Slack.
>
> Why is it needed? Lots of reasons that are elaborated in the motivations
> page of the wiki but one of the most urgent is that Slack has adopted a
> policy of closing community teams to new members once they get large
> (anecdotally around 7000 members) and the Clojurians Slack channel is
> already over 4800.
>
>
> On 2 Feb 2016, at 08:22, Mikera  wrote:
>
> If you are interested in data science, help with core.matrix and the
> associated libraries is always appreciated, and we are very
> contributor-friendly in the numerical Clojure community.
>
> On Monday, 1 February 2016 18:51:37 UTC+8, Steven Deobald wrote:
>>
>> Hey folks!
>>
>> Today is the first day nilenso has ever had an intern on-staff. He's been
>> in the industry for a few years but he's relatively new to Clojure. We try
>> to ramp people up as slowly and supportively as possible. For interns, we
>> figure writing (and re-writing, natch) open source is the safest place to
>> start.
>>
>> With that context set, does anyone on the list have suggestions for
>> projects we can guide him through? We will be working with him through some
>> the standard Clojure literature over the coming months, as well as
>> providing guidance with his patches/pull-requests.
>>
>> We're open to any shape of project: applications, libraries, tools. If
>> you have a Clojure project you would like help with (or that you wish
>> someone would start), we would love to evaluate it as a learning
>> opportunity.
>>
>> Thanks everyone!
>>
>> Steven Deobald -- ⌀ -- nilenso.com
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "London Clojurians" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to london-clojurians+unsubscr...@googlegroups.com.
> To post to this group, send email to london-clojuri...@googlegroups.com.
> Visit this group at https://groups.google.com/group/london-clojurians.
> 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 beyond Java 6 ?

[Bozhidar Batsov]

Even Java 1.7 already reached its end of life. I get it that some companies
are slow to update their infrastructures, but being constrained to legacy
unsupported systems adds both a security risk and some development
overhead. It's high time for Java 1.6 to be laid down to rest and for
people stuck to it to move forward. I'm guessing Cognitect's enterprise
customers are the primary reason 1.6 is still supported.

On 20 January 2016 at 08:58, Max Penet  wrote:

> I doubt it such a big deal actually.
>
> You can run multiple versions of the java on the same machine. The
> only issue would be for legacy projects that are frozen to java 6 and
> would like to upgrade to a lib (like clojure) relying java8.  But I
> doubt such projects are the norm, and the few that are probably do not
> care about upgrading to the latest clojure.
>
> There are a lot of very large projects (such as Jetty, Cassandra, etc)
> that just made java8 a requirement for their next/current releases, and I
> don't see much complaining about it (quite the opposite).
>
> Also the fact that clojure itself is not getting an avalanche of new
> feature at every release makes upgrading not so critical.
>
>
>
>
> On Tuesday, January 19, 2016 at 8:33:56 PM UTC+1, Sean Corfield wrote:
>>
>> Didier wrote on Tuesday, January 19, 2016 at 11:08 AM:
>>
>> Why not make new versions of Clojure support the latest Java version and
>> JDK features
>>
>>
>> Since Clojure 1.7 (and 1.8) run on Java 8 quite happily, I assume you
>> mean "Why not drop support for earlier Java versions with each new version
>> of Clojure"?
>>
>> The answer — for any situation like this — is that many companies are
>> slow to upgrade fundamental infrastructure like the JVM because they have
>> so many things that rely on it, so it is a major exercise. For Clojure to
>> be adopted by such companies, it needs to run on their existing JVM
>> infrastructure.
>>
>> Dropping support for older JVM versions is therefore a Big Deal(™) and
>> can not be undertaken lightly. A lot of software generally tries to support
>> current plus two versions back which would mean Java 6 support should
>> likely stay until Java 9 is GA (although it’s true that there is also a lot
>> of software that only supports current plus one version back).
>>
>> Bear in mind that there are many companies still running Windows XP
>> because upgrading is such an expensive business (in time and effort, as
>> well as any actual costs)!
>>
>> Sean Corfield -- (904) 302-SEAN
>> An Architect's View -- http://corfield.org/
>>
>> "Perfection is the enemy of the good."
>> -- Gustave Flaubert, French realist novelist (1821-1880)
>>
>> --
> 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] New clojure.org!

[Bozhidar Batsov]

Great work! This was long overdue, but I'm extremely happy we made this
solid first step!

On 15 January 2016 at 04:11, Eunmin Kim  wrote:

> Great!!
>
> --
> 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.10 is out!

[Bozhidar Batsov]

This is the commit you're looking for
https://github.com/clojure-emacs/cider-nrepl/commit/fbcecbaf10bb55aae875f93810b67b41c833da21
:-)

On 22 December 2015 at 21:38, Daniel Szmulewicz <daniel.szmulew...@gmail.com
> wrote:

> I don't know which commit did it, but I noticed that cider has greatly
> improved its integration with boot-clj. Previously, M-. (find-tag,
> find-symbol) would look for the symbol in the immutable fileset, now it
> goes to the filesystem. That is fantastic.
>
> Daniel
>
>
>
> On Thursday, December 3, 2015 at 8:00:06 PM UTC+2, Bozhidar Batsov wrote:
>
>> Hey everyone,
>>
>> CIDER 0.10 (a.k.a. CIDERX) is finally out!
>>
>> We've got a ton of new features and I hope you're going to love it!
>>
>> The changelog is here
>> https://github.com/clojure-emacs/cider/releases/tag/v0.10.0
>>
>> You can also check out this presentation
>> https://speakerdeck.com/bbatsov/cider-the-story-so-far-and-the-road-ahead
>>
>> Enjoy!
>>
>

-- 
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] 2015 State of Clojure Community survey

[Bozhidar Batsov]

"Emacs + inferior-lisp" should be renamed to "Emacs + inf-clojure".
clojure-mode no longer works with inferior-lisp.

On 4 December 2015 at 16:44, James Reeves  wrote:

> What does this question mean, exactly?
>
> 6. What types of applications do you use Clojure, ClojureScript, or
>> ClojureCLR in?
>>
>> Company-wide/Enterprise
>> Departmental
>> Team
>> Personal
>
>
> - James
>
> On 4 December 2015 at 16:31, Alex Miller  wrote:
>
>> If you are a user of Clojure, ClojureScript, or ClojureCLR, we are
>> greatly interested in your responses to the following survey:
>>
>> https://www.surveymonkey.com/r/clojure-2015
>>
>> The survey contains four pages:
>>
>> 1. General questions applicable to any user of Clojure, ClojureScript, or
>> ClojureCLR
>> 2. Questions specific to the JVM Clojure (skip if not applicable)
>> 3. Questions specific to ClojureScript (skip if not applicable)
>> 4. Final comments
>>
>> The survey will close December 18th. Afterwards we will release all of
>> the data and some analysis.
>>
>> Many thanks to Chas Emerick for starting and keeping this survey going
>> for so many years!
>>
>> --
>> 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.

CIDER 0.10 is out!

[Bozhidar Batsov]

Hey everyone,

CIDER 0.10 (a.k.a. CIDERX) is finally out!

We've got a ton of new features and I hope you're going to love it!

The changelog is here
https://github.com/clojure-emacs/cider/releases/tag/v0.10.0

You can also check out this presentation
https://speakerdeck.com/bbatsov/cider-the-story-so-far-and-the-road-ahead

Enjoy!

-- 
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: Current Cider SNAPSHOT not working??

[Bozhidar Batsov]

Did you go over the instructions here
https://github.com/bhauman/lein-figwheel/wiki/Using-the-Figwheel-REPL-within-NRepl
?

On 27 November 2015 at 23:33, alexander adhyatma 
wrote:

> you need to add com.cemerick/piggieback to the project.clj (dependency
> section) as well as adding cider/cider-nrepl "0.10.0-SNAPSHOT" and
> refactor-nrepl to the plugin section.
> then in the :figwheel section, you need to add
>
> :nrepl-middleware ["cemerick.piggieback/wrap-cljs-repl"
> "cider.nrepl/cider-middleware" "refactor-nrepl.middleware/wrap-refactor"]
>
> should be running great.
>
>
> On Friday, November 27, 2015 at 7:53:32 PM UTC+7, Karel Miarka wrote:
>>
>> The plugins were pulled, cider namespace required, everything is OK when
>> I connect from Cider to "lein repl". Works fine in both spacemacs and
>> prelude.
>>
>> Both cider & refactor middleware warnings occur only in spacemacs when I
>> start "lein figwheel" with nREPL as I'm used to.
>> In prelude there was only the cider middleware warning, refactor was not
>> complaining.
>> In spacemacs both warnings appear also with clojure-emacs/example-config
>> which uses 0.9.1 Cider release when connecting agains "lein figwheel".
>>
>> It worked fine with my old 32bit setup. I used to run just "lein
>> figwheel" for both server and client to save memory. And then connected to
>> the nREPL 2x and run figwheel.side-car/cljs-repl in one of them.
>>
>> Thanks for the help. I will try to play with my project.clj file or solve
>> it by running "lein repl" for the server and "lein figwheel" for the client
>> part.
>>
>> On Friday, November 27, 2015 at 12:56:00 AM UTC+1, Artur Malabarba wrote:
>>>
>>> Looks like your plugins are not getting pulled by leiningen.
>>>
>>> Delete your .m2/ snapshots and then start lein repl in a terminal. Do
>>> you see the plugins being pulled?
>>>
>>> In this repl, are you able to require cider namespaces? Try: (require
>>> 'cider.nrepl.middleware.debug)
>>>
>>> --
> 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: Need help setting up Emacs for Clojure on Windows 8

[Bozhidar Batsov]

I guess it won't hurt if we added a few more pointers for Windows users.
Lars, you're using Windows occasionally, right? I guess you can write a few
paragraphs in the README about the common problems people might run into on
Windows.

On 27 October 2015 at 02:02, Tina Ramsey  wrote:

> That Reddit post did help, thanks. I have a HOME environment variable set
> up on Windows so I can use ~ anywhere, so that wasn't the problem, but when
> I opened my clojure project and ran M-x cider-jack-in it opened the repl. I
> guess the configs did run properly, even though I didn't get any
> indication? And I had no clue about cider-jack-in ... not sure how I was
> supposed to figure that out! Thanks for your help! Luckily I don't have to
> write that much Clojure on my work machine, because I'm really enjoying
> learning it but so far everything, including installing Clojure itself and
> Leiningen, has gone pretty rough for me on Windows.
>
>
> On Monday, October 26, 2015 at 11:17:52 AM UTC-7, David Powell wrote:
>>
>>
>> (There shouldn't actually be any problem using ~ from within emacs in
>> Windows though - emacs will automatically handle it - I do it all the
>> time.  It is probably related to emacs using
>> "C:\Users\jason\AppData\Roaming" as its home directory though.)
>>
>> On Mon, Oct 26, 2015 at 6:09 PM, Daniel Higginbotham 
>> wrote:
>> >
>> > Sorry you're having trouble! Does this help?
>> https://www.reddit.com/r/Clojure/comments/3pn3fo/clojure_for_the_brave_and_true_updated_to_match/cw8h8qy
>> >
>>
> --
> 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: deprecation warnings?

[Bozhidar Batsov]

You should! It will be the biggest and greatest CIDER release ever. It will
likely be the most postponed release ever as well. :-)

On 21 October 2015 at 04:42, James Elliott  wrote:

> Sweet, I’m starting to really look forward to that release. :D
>
>
> On Monday, October 19, 2015 at 10:54:04 AM UTC-5, Lars Andersen wrote:
>>
>> Font-locking of deprecated vars was just added to CIDER.  It's available
>> in snapshots now, and will be included in 0.10.
>>
>> On Wednesday, October 14, 2015 at 6:09:21 PM UTC+2, William la Forge
>> wrote:
>>>
>>> Going forward, I'd like to deprecate some functions and have a warning
>>> displayed on first use. So I've done this:
>>>
>>> (def emptyAAMap ^{:deprecated "0.3.4"}
>>>   (new AAMap emptyNode {:comparator RT/DEFAULT_COMPARATOR}))
>>>
>>>
>>> But I am not seeing any warnings from either lein or cursive. Do I need
>>> to add a plugin?
>>>
>>> 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: Where I can learn this?

[Bozhidar Batsov]

Just a small clarification - clj-refactor.el is currently an extension for
CIDER, although there are plans to merge at least some of its functionality
in CIDER (or provide similar functionality there out-of-the-box).

On 15 October 2015 at 09:19, Mikhail Malchevskiy  wrote:

> Sure you can =) Here is the public repo of Magnar Sveen (author of the
> "Parens of the Dead"): https://github.com/magnars/.emacs.d.
> Some of the functions are part of the clj-refactor (
> https://github.com/clojure-emacs/clj-refactor.el) which is part of the
> CIDER (https://github.com/clojure-emacs/cider)
> My personal recommendation would be to try Spacemacs (
> https://github.com/syl20bnr/spacemacs) which is great by itself and also
> has very pretty default setup for clojure (you just need to add clojure
> layer)
>
> четверг, 15 октября 2015 г., 4:48:37 UTC+3 пользователь Erlis Vidal
> написал:
>
>> Guys,
>>
>> I've just finished the first episode of "parens of the dead" and was mind
>> blown for what I saw there.
>>
>> http://www.parens-of-the-dead.com/e1.html
>>
>> Have you been near someone that do something cool and you have to ask,
>> "how you did that?" Well, every second on the video I was having that
>> feeling. I don't work much in clojure, just in my spare time, is my dream
>> language, I use it in emacs, but I'm really not using any of the things I
>> saw in the video.
>>
>> - html completion
>> - refactoring (rename, move to function)
>> - adding dependencies and automatic project.clj modificaiton
>>
>> Is there a way I can learn what emacs packages was used for all that?
>>
>> I know this is not a clojure question but I'll die to have a screencast
>> that teach all those keystrokes and reveal the real power of emacs +
>> clojure.
>>
>> It was really nice to see the mouse in the middle of the screen and not
>> moving at all. :D
>>
>> Thanks for sharing! In just 11 minutes you empowered my Clojure passion
>> even more!
>>
>> Erlis
>>
> --
> 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-nrepl not installed (emacs24)

[Bozhidar Batsov]

It's usually a good idea to get familiar with the first few sections of any
project's README. :-)

On 19 September 2015 at 19:04, Mauricio Aldazosa <
mauricio.aldaz...@gmail.com> wrote:

> Hi,
>
> cider-nrepl is some middleware that sits outside emacs. You can use it via
> leiningen or boot. Take a look at the instructions here:
> https://github.com/clojure-emacs/cider#cider-nrepl-middleware
>
> Happy hacking,
> Mauricio
>
> ​
>
> --
> 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: Using metadata to specify how calls to a macro should be indented

[Bozhidar Batsov]

I'm kind of puzzled by the last couple of responses. Obviously very few
forms (probably only macros) would have indentation specifications and
editors can certainly disregard them, so I don't see the code being
littered with indentation specs any time soon or some indentation being
forced on everyone.

This idea is not something new - in Emacs Lisp there's a way to specify the
indentation of a macro form which is pretty similar (via `declare`). Maybe
there was something similar for CL as well, but right now I'm not 100% sure.

As for things like the one-space indent, I'm not sure how related they are
to Emacs's prominence in the Lisp world. It sounds more plausible that such
conventions were established before the age of `lisp-mode`.

On 17 September 2015 at 08:31, Colin Fleming 
wrote:

> Unfortunately as tools developers we can't force our indentation
> preferences on our users, although I'd be fine with it if you convinced
> everyone to just use two spaces for everything, even though it's not my
> preferred formatting. Cursive has supported this for ages (copied from
> Emacs) but I don't know how many people actually use it.
>
> As above, I agree that this shouldn't be in the code.
>
> I also agree very strongly that this shouldn't just adopt whatever Emacs
> does for formatting. The one-space indent for list forms, in particular,
> drives me nuts and is purely an implementation detail, not because that
> makes any sort of sense for code.
>
> You're right that the format spec is pretty obtuse, although we have far
> worse out there (the pprint format, ahem). Separating the format spec out
> into a separate doc would allow something more verbose to be used which
> could be more expressive.
>
> On 16 September 2015 at 23:34, Chas Emerick  wrote:
>
>> Hi all; here to satisfy the quarterly quota to maintain my status as
>> "that guy".
>>
>> This is a questionable proposal. It:
>>
>> * introduces completely orthogonal, transient concerns (presentation)
>> into code, ideally a canonical, long-lived source-of-truth
>> * sets up a bikeshed at the top of every def* form
>> * adopts idiosyncratic implementation details of a particular editor's
>> language support (the defrecord example's :indent is particularly obtuse
>> IMO, even if you are aware of how clojure-mode is implemented)
>>
>> I *think* I coined the "always two spaces" shorthand for the (admittedly,
>> minority) position that list forms should be formatted completely
>> regularly, so as to:
>>
>> * make formatting a trivial operation, not requiring any "real" reading
>> * eliminate this entire topic
>>
>> Here's the first time I talked about this IIRC:
>> https://groups.google.com/forum/#!msg/clojuredev-users/NzKTeY722-I/3hmNvJulcksJ
>>
>> Best,
>>
>> - Chas
>>
>>
>> On 09/13/2015 06:06 AM, Artur Malabarba wrote:
>>
>> Hi everyone,
>>
>>
>> Over at CIDER we're adding a feature where the author of a macro (or
>> function) can specify how that macro should be indented by adding an
>> :indent metadata to its definition. This way the editor (and other
>> tools, like cljfmt) will know what's the proper way of indenting any macro
>> (even those custom-defined) without having to hardcode a bajillion names.
>>
>> Here's an example of how you specify the indent spec for your macros
>>
>>
>> (defmacro with-out-str
>>   "[DOCSTRING]"
>>   {:indent 0}
>>   [& body]
>>   ...cut for brevity...)
>>
>> (defmacro defrecord
>>   "[DOCSTRING]"
>>   {:indent [2 nil nil [1]]}
>>   [name fields & opts+specs]
>>   ...cut for brevity)
>>
>> (defmacro with-in-str
>>   "[DOCSTRING]"
>>   {:indent 1}
>>   [s & body]
>>   ...cut for brevity...)
>>
>>
>> We'd like to hear any opinions on the practicality of this (specially
>> from authors of other editors).
>> Below, I'll be saying “macros” all the time, but this applies just the
>> same to functions.
>>
>> *Special arguments*
>>
>>
>> Many macros have a number of “special” arguments, followed by an
>> arbitrary number of “non-special” arguments (sometimes called the body).
>> The “non-special” arguments have a small indentation (usually 2 spaces).
>> These special arguments are usually on the same line as the macro name,
>> but, when necessary, they are placed on a separate line with additional
>> indentation.
>>
>> For instance, defrecord has two special arguments, and here's how it
>> might be indented:
>>
>>
>> (defrecord TheNameOfTheRecord
>> [a pretty long argument list]
>>   SomeType
>>   (assoc [_ x]
>> (.assoc pretty x 10)))
>>
>>
>> Here's another way one could do it:
>>
>>
>> (defrecord TheNameOfTheRecord
>>[a pretty long argument list]
>>   SomeType
>>   (assoc [_ x]
>> (.assoc pretty x 10)))
>>
>>
>> *The point of the indent spec is not to specify how many spaces to use.*
>>
>>
>> The point is just to say “a defrecord has *2* special arguments”, and
>> then let the editor and the user come to an agreement on how many spaces
>> they like to use 

Re: Using metadata to specify how calls to a macro should be indented

[Bozhidar Batsov]

It's probably obvious, but let me say it just in case it isn't - I'm super
supportive of Artur's idea. I've been thinking about something similar for
a while and I believe deciding on something that's going to be used by many
Clojure tools (CIDER, Cursive, fireplace, ccw, cljfmt, etc) will be hugely
beneficial for everyone. As for the spec itself - I'd only suggest using
some keyword instead of `nil`, as it would probably be more intention
revealing.

I have no preference about the name of the metadata key itself.

On 13 September 2015 at 13:15, Colin Yates  wrote:

> My knee-jerk reaction is:
>  - +10
>  - leaving it up to the user is absolutely the right thing to do
>  - the name ‘indent’ and what it is actually capturing are at different
> levels of abstraction. Possibly ‘structure’ might be a better name as that
> is what it is describing?
>
> But don’t listen to a word I say - I am hacking through some of my old
> code which uses :admission-date and :start-date interchangeably *for the
> same data structure* - sigh.
>
> My 1.5 cents.
>
> On 13 Sep 2015, at 11:06 AM, Artur Malabarba 
> wrote:
>
> Hi everyone,
>
>
> Over at CIDER we're adding a feature where the author of a macro (or
> function) can specify how that macro should be indented by adding an
> :indent metadata to its definition. This way the editor (and other tools,
> like cljfmt) will know what's the proper way of indenting any macro (even
> those custom-defined) without having to hardcode a bajillion names.
>
> Here's an example of how you specify the indent spec for your macros
>
>
> (defmacro with-out-str
>   "[DOCSTRING]"
>   {:indent 0}
>   [& body]
>   ...cut for brevity...)
>
> (defmacro defrecord
>   "[DOCSTRING]"
>   {:indent [2 nil nil [1]]}
>   [name fields & opts+specs]
>   ...cut for brevity)
>
> (defmacro with-in-str
>   "[DOCSTRING]"
>   {:indent 1}
>   [s & body]
>   ...cut for brevity...)
>
>
> We'd like to hear any opinions on the practicality of this (specially from
> authors of other editors).
> Below, I'll be saying “macros” all the time, but this applies just the
> same to functions.
>
> *Special arguments*
>
>
> Many macros have a number of “special” arguments, followed by an arbitrary
> number of “non-special” arguments (sometimes called the body). The
> “non-special” arguments have a small indentation (usually 2 spaces). These
> special arguments are usually on the same line as the macro name, but, when
> necessary, they are placed on a separate line with additional indentation.
>
> For instance, defrecord has two special arguments, and here's how it
> might be indented:
>
>
> (defrecord TheNameOfTheRecord
> [a pretty long argument list]
>   SomeType
>   (assoc [_ x]
> (.assoc pretty x 10)))
>
>
> Here's another way one could do it:
>
>
> (defrecord TheNameOfTheRecord
>[a pretty long argument list]
>   SomeType
>   (assoc [_ x]
> (.assoc pretty x 10)))
>
>
> *The point of the indent spec is not to specify how many spaces to use.*
>
>
> The point is just to say “a defrecord has *2* special arguments”, and
> then let the editor and the user come to an agreement on how many spaces
> they like to use for special and non-special arguments.
>
> *Internal indentation*
>
>
> The issue goes a bit deeper. Note the last argument in that defrecord. A
> regular function call would be internally indented as
>
> (assoc [_ x]
>(.assoc pretty x 10))
>
> But this is not a regular function call, it's a definition. So we want to
> specify this form internally has 1 special argument (the arglist vector),
> so that it will be indented like this:
>
> (assoc [_ x]
>   (.assoc pretty x 10))
>
> The indent spec we're working on does this as well. It lets you specify
> that, for each argument beyond the 2nd, if it is a form, it should be
> internally indented as if it had 1 special argument.
>
> *The spec*
>
>
> An indent spec can be:
>
>- nil (or absent), meaning *“indent like a regular function call”*.
>- A vector (or list) meaning that this function/macro takes a number
>of special arguments, and then all other arguments are non-special.
>   - The first element of this vector is an integer indicating how
>   many special arguments this function/macro takes.
>   - Each following element is an indent spec on its own, and it
>   applies to the argument on the same position as this element. So, when 
> that
>   argument is a form, this element specifies how to indent that form
>   internally (if it's not a form the spec is irrelevant).
>   - If the function/macro has more aguments than the vector has
>   elements, the last element of the vector applies to all remaining 
> arguments.
>- If the whole spec is just an integer n, that is shorthand for [n].
>
>
> *Examples*
>
>
> So, for instance, if I specify the defrecord spec as [2 nil nil [1]],
> this is saying:
>
>- defrecord has 2 special arguments
>- The 

Re: 0.1.0 core.async release?

[Bozhidar Batsov]

On 8 August 2015 at 11:42, Sean Corfield s...@corfield.org wrote:

 - test-all: isn't there an existing support for launching tests in
 clojure-maven-plugin-maven-plugins ? Naive question: in your current
 workflow, you relaunch the Lein executable each time via an emacs command?
 Or is it via an nrepl client session connected to the same repl that emacs
 uses for your own user interactions?


 Test-all is just an alias in Leiningen. It can be any series of tasks. It
 was an example of a command line that I want to be able to run that isn’t
 mvn test.

 - test-all: is there, and do you use, a mode which automatically
 relaunches the tests when source code changes are detected on the
 filesystem?


 No, generally I don’t.

 - jack in: is that the term in emacs for an action which will connect to
 a repl (the repl? - sorry for my lack of knowledge), and potentially
 start a new jvm process for the project under development (bu starting
 leiningen via its shell script or maybe crating the command line for
 calling java clojure.main -i leiningen.main/-main ?)


 Yes, jack-in is an nrepl/cider term for starting a REPL (with Leiningen)
 using the current project.clj.


Just a small clarification - it's a term involving starting a local nREPL
server for the current project and connecting to it. You don't really have
to use lein for this - boot is also supported out-of-the-box and in theory
every command creating an nREPL server would work.



 Basically I want contrib projects to be as easy to work with as
 non-contrib projects (which all have project.clj files and use Leiningen)
 and that’s why I have project.clj for clojure.java.jdbc. I have a variety
 of dependencies in project.clj that might be different to the pom.xml
 because I run a different set of tests etc. For example I have the MS SQL
 JDBC library installed locally and I test against a VM running XP and SQL
 Server. That’s not relevant for the pom.xml.

 I’m not interested in using Maven for this: Maven is a necessary evil as
 far as I’m concerned for the build server. I also don’t want to use Eclipse
 or IntelliJ or any of those Java IDEs.

 I wish Clojure/core would support Leiningen fully and use it for the build
 system and for Sonatype / Maven Central deployments so we didn’t need
 pom.xml at all.

 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.

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 the.stuart.sie...@gmail.com 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
 http://dev.clojure.org/jira/browse/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: 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 dbut...@gmail.com 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: [:ann :book] ClojureScript Unraveled

[Bozhidar Batsov]

Sounds like a plan to me. :-)

On 21 July 2015 at 18:16, Alejandro Gómez alejan...@dialelo.com 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 alejan...@dialelo.com 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 alejan...@dialelo.com
 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

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 colin.mailingl...@gmail.com 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 lprefonta...@softaddicts.ca
 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 brobro...@gmail.com 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
  lprefonta...@softaddicts.ca 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 receiving emails from it, send
 an email to clojure+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

 

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 alejan...@dialelo.com 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 alejan...@dialelo.com
 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.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the 

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

[Bozhidar Batsov]

On 18 July 2015 at 14:13, Andrey Antukh n...@niwi.nz 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 - Андрей Антух - n...@niwi.nz
 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 - Андрей Антух - ni...@niwi.nz javascript:
 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:48, Colin Yates colin.ya...@gmail.com 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 lprefonta...@softaddicts.ca
 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 n...@niwi.nz 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 - Андрей Антух - n...@niwi.nz
 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
 

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

[Bozhidar Batsov]

On 18 July 2015 at 20:18, Luc Prefontaine lprefonta...@softaddicts.ca
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 n...@niwi.nz wrote:

  On Sat, Jul 18, 2015 at 6:48 PM, Colin Yates colin.ya...@gmail.com
  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 the possibility of the
  inclusion of some requested 

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

[Bozhidar Batsov]

On 18 July 2015 at 22:52, Luc Préfontaine lprefonta...@softaddicts.ca
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 bozhi...@batsov.com wrote:

 On 18 July 2015 at 20:18, Luc Prefontaine lprefonta...@softaddicts.ca
 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

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

[Bozhidar Batsov]

On 18 July 2015 at 18:44, Luc Prefontaine lprefonta...@softaddicts.ca
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 n...@niwi.nz 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 

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 ritchie...@gmail.com 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.

[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 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 dtouc...@gmail.com 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 dtouc...@gmail.com 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 dtou...@gmail.com 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.

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 phill.w...@gmail.com 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 flexibe...@gmail.com 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: 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 magn...@gmail.com 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] 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 b.gh...@gmail.com 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 bozhi...@batsov.com
 wrote:
  Happy to hear this! :-)
 
  On 18 June 2015 at 14:36, Stefan Kamphausen ska2...@gmail.com 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]

Happy to hear this! :-)

On 18 June 2015 at 14:36, Stefan Kamphausen ska2...@gmail.com 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]

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 grapenthinl...@gmail.com 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 bozh...@batsov.com
 wrote:
  Happy to hear this! :-)
 
  On 18 June 2015 at 14:36, Stefan Kamphausen ska...@gmail.com 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] 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 flexibe...@gmail.com wrote:


 Bozhidar Batsov bozhi...@batsov.com 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]

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 maverick.avice...@gmail.com 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]

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 grapenthinl...@gmail.com 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]

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 a2093...@trbvm.com 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]

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 ndtm.i...@gmail.com 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.

[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: [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 joshnet2...@gmail.com 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 ja...@decomplecting.org
 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 xav...@maillard.im 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.

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 a...@diligenceengine.com 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: 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 dmiller2...@gmail.com 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: [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 phillip.l...@newcastle.ac.uk wrote:

 richard.mo...@posteo.de 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: [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 blak3mil...@gmail.com 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: [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 dnolen.li...@gmail.com wrote:

 Yep, the clojure.main option is the one you want.

 David

 On Sat, Apr 11, 2015 at 10:45 AM, Georgi Danov georgi.da...@gmail.com
 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 georgi...@gmail.com
 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] 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 dskoz...@gmail.com 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.