Yeah, that's an unfortunate problem with package.el. See
https://github.com/clojure-emacs/cider/issues/1050#issuecomment-112595451
On 17 June 2015 at 05:38, Avi Avicenna wrote:
> Wow!! Many thanks to all CIDER contributors.
>
> I didn't get it to work at first, but deleting all previous *.elc fi
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 fina
I've been working on a Ring app that involves storing sessions as cookies,
and within the session there are a couple Java objects that implement
java.io.Serializable. I was somewhat surprised to find that the print-dup
multimethod didn't have native support for Java Serializables, though I can
Don't bother please, after I upgraded the clojure-mode issue got fixed.
Again thanks for your magnificent tool.
Best regards
Shahrdad
On Tue, Jun 16, 2015 at 12:19 PM, Shahrdad Shadab
wrote:
> Hi Bozhidar
>
> Thanks for the awesome work however when I upgraded to version 0.9 I get
> the followi
Hi Bozhidar
Thanks for the awesome work however when I upgraded to version 0.9 I get
the following error when starting cider in emacs:
Starting nREPL server via lein repl :headless...
nREPL server started on 55266
nREPL: Establishing direct connection to localhost:55266 ...
nREPL: Direct connecti
Answering my own question about performance, it looks like almost 14 seconds
for the Lambda function to run. Doing the math[fn:1] if I were to run this
300 times in a month bill would be about $342.56. Probably not the ideal
solution for clojure in the cloud just yet. :)
#+BEGIN_EXAMPLE
Nice work! Can you give any indication of what performance is like?
Kyle Sexton
Ragnar Dahlén writes:
> I gave it a go:
> https://github.com/uswitch/lambada
>
> It's just a POC. Needed a Java shim to manage class loaders so the
> interface is not as nice I was hoping.
>
> Might make it into l
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 cloju
I gave it a go:
https://github.com/uswitch/lambada
It's just a POC. Needed a Java shim to manage class loaders so the
interface is not as nice I was hoping.
Might make it into library if there's interest.
On Monday, 15 June 2015 21:07:29 UTC+1, Kyle Sexton wrote:
>
> Curious if anyone is doing
Well, that was the theory, anyway :)
The practice shows that the handwritten library supports 100% the latest
OpenCL version, while a couple of automatically generated libraries (Jogamp
JOCL, JavaCL) support only old versions, and even that support is not
complete. And it is written in standard
Ah thanks James, I missed the pending nil. The actual value is still nil
indeed:
user=> (def m (re-matches #".*(foo\.gif).*" "foo.gif\n"))
"foo.gif\n"#'user/m
user=> m
nil
Not sure what would be the cause here then, but the random printing of the
second argument of re-matches also happens when I
On 16 June 2015 at 10:19, Jeroen van Dijk
wrote:
> I came accross this weird case below with re-matches (in clojure 1.6). For
> some reason the pattern matches, once just once, only after a parse
> exception. This pattern repeats with every follow up parse exception. Is
> this a known bug? It see
I name all of my protocols as active very in the first tense/descriptions of
what they do. Rather than ‘Find’ I would have ‘IFindThings’. It takes a bit of
getting used to and it was a suggestion in something I read a while ago (one of
Steve Yeggies’ posts maybe?) but it really makes you think,
On Tuesday, 16 June, 2015 at 5:19 pm, Jeroen van Dijk wrote:
> I came accross this weird case below with re-matches (in clojure 1.6). For
> some reason the pattern matches, once just once, only after a parse
> exception. This pattern repeats with every follow up parse exception. Is this
> a k
Understood- almost all the functions in the zk namespace were intended for
occasional/admin type use so they open/close the ZK connection.
It should be pretty easy to refactor that around so connections are passed
in (allowing you to retain a connection across multiple operations).
I'll see if
I came accross this weird case below with re-matches (in clojure 1.6). For
some reason the pattern matches, once just once, only after a parse
exception. This pattern repeats with every follow up parse exception. Is
this a known bug? It seems to be related with the pending newline too.
user=> (re-
16 matches
Mail list logo
