Yes, that's correct.
On 12 April 2017 at 17:56, Didier wrote:
> @Colin If I understand correctly, if I buy the personal license I can use
> it for my own commercial projects, but I can also use it at my work, to
> work on their code base, as long as I'm the one using it. Is that correct?
> I pro
@Colin If I understand correctly, if I buy the personal license I can use it
for my own commercial projects, but I can also use it at my work, to work on
their code base, as long as I'm the one using it. Is that correct? I probably
can't convince work to buy into a bunch of licenses, but I'd lov
Awesome, time for me to try Cursive.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe
I spoke about it at Clojure/West:
https://www.youtube.com/watch?v=ql77RwhcCK0. I talked there about some of
the limitations, but it works really nicely for the most part.
CIDER actually has a nice debugger these days too. It works in a very
different way, via source instrumentation. It works bette
Cursive has had a really good debugger for a long time. I don't use it
much, but when I need it it *just works*.
Timothy
On Tue, Apr 11, 2017 at 7:37 PM, Didier wrote:
> A good debugger is indeed extremely useful for Clojure - I use one every
>> day :-)
>>
>
> Am I living in the past? I thought
>
> A good debugger is indeed extremely useful for Clojure - I use one every
> day :-)
>
Am I living in the past? I thought Clojure didn't have a way to step
through code interactively?
On Tuesday, 11 April 2017 16:30:14 UTC-7, Colin Fleming wrote:
>
> A good debugger is indeed extremely usef
A good debugger is indeed extremely useful for Clojure - I use one every
day :-)
On 12 April 2017 at 05:29, Didier wrote:
> Experimentation is good. This is indeed surprising. I think it shows that
> a good debugger would still sometime be useful in Clojure. I can't really
> explain what's happe
Experimentation is good. This is indeed surprising. I think it shows that a
good debugger would still sometime be useful in Clojure. I can't really explain
what's happening.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, sen
понедельник, 10 апреля 2017 г., 22:56:43 UTC+2 пользователь Didier написал:
>
> Hum, not sure why you would do this, but I'm guessing refresh goes in an
> infinite async loop. You keep reloading a namespace which creates a thread
> to reload itself.
>
> I can't really explain why the symbol exist
You're reloading your namespaces from a non-repl thread, concurrently while
editing code in the repl. I don't think this is use case is supported by
tools.namespace.
On Mon, Apr 10, 2017 at 2:56 PM, Didier wrote:
> Hum, not sure why you would do this, but I'm guessing refresh goes in an
> infini
10 matches
Mail list logo
