i'm working on a patch for cider to issue a warning if the clojure version is not supported by looking through project.clj and build.boot files. My regex: "org.clojure/clojure\s-*\".*\"" works just fine. But when i add the capturing group, it can break: "org.clojure/clojure\s-*\"\\(.*\\)\"". Does anyone have any thoughts on this?

it breaks on the build.boot file for cprop which has the line: :dependencies '[[org.clojure/clojure "1.8.0"]

but it works without the capturing group. The capturing group version works on all other examples that i have

i've got this one now. It seems to work when i call it directly but not when my functions do: "org.clojure/clojure\s-*\"\([\.0-9]+\)\""

Well, in the future, if you are wondering, emacs regexes are dumb and require many slashes. "org.clojure/clojure\\s-*\"\\([.0-9]+\\)\""

i'm still not sure if the single slash double quote is a ticking time bomb or not

no

it's fine

the thing is that emacs regexps are strings

so if you want a regexp with a backslash, (like \(), you need to escape that backslash

because \( is the same as ( in strings

it's a single char

thanks malabarba. I'm gonna write a few tests tonight and then submit the pull request

so you need to write \\( in the string

so that the regexp engine actually sees the \\

i've also seen that if you are lacking boot and try to run cider-jack-in, you get back a wrong argument stringp message instead of something useful

so that'll be my next quality of life feature for cider

nice

yeah the hammer dropped on me when you explained that. I understand the significance of different syntaxes for regexes in other languages now

indeed

as for the clojure-version thingy. I feel almost bad saying this, considering the pain you had with regexps, but I think there's a better way to do it.

i learned. so even if the code itself is thrown away no biggie

are you going to ask nrepl what version of clojure is loaded?

If you jack-in to a project with an old clojure-version, does evaluation still work?

i thought about that but worried that if there was an error it may not be able to report it

it does, but with the error message i posted a screenshot of

ok

where it complains about an nrepl mismatch

and some things break

notably M-, navigation

Then I think the best approach is to run (cider-nrepl-sync-request:eval "*clojure-version*")

haha. yeah you're probably right

This will return the proper clojure version being used

and then it looks like those responses are put into a dictionary or hashmap somewhere, is that correct?

Yes, but that's not how you use them

oh ok

with async requests you would have to use a callback

but with sync request the respoinse is simply returned directly

so you could do something like this

`

(let* ((response (cider-nrepl-sync-request:eval "*clojure-version*"))
       (clojure-version (nrepl-dict-get response "value")))
  (complain about clojure-version))

I also saw that there is a version< function out there. I see that explicitly clojure versions 1.7.0 and 1.8.0 are supported. I used these values explicitly rather than set a benchmark of > 1.7.0 as i'm not sure how many point releases of clojure are released, and if it would ever be possible to support say 1.7.0, not 1.7.1, 1.8.0, etc

but i may just make it along the lines get clojure version, complain if version< cider-minimum-clojure-version

Yes, use version<

I was going to say that too

thanks so much for the pointers

I was on my phone yesterday so couldn't type much

and huge thanks for all your work on the debugger and general help on the dev mailing list. you are a rockstar man

thanks

After the recence talk about types at Clojure/West, I would like to ask here how and what folks use for racket in emacs? There in geiser and racket-mode. Ideally I would like to keep the cider workflow :)

what do you mean by cider workflow?

but in general things work like slime/cider, etc with repl's and emacs

you create a server, connect over sockets, and emacs nicely sends info back and forth

Slime? What is this 2011?

Emacs? What is this 1975?

ah ah

wut? we can't bash common lisp in here

this is an emacs channel about clojure haha

I tried geiser but I think I will need to add quack and change a lot of key bindings

oh too bad, Paredit does not like typed clojure

what's the problem with paredit and typed clojure?

oh yeah. that's why i had to get rid of lispy. the [ characters are a navigation command and not a printing character in that mode.

smartparens works and oh...did not know about modules, that is why it was not finding my symbols 😄

I use geiser and it’s nice enough. i don’t code in Racket that often though

geiser is pretty similar to cider

they even have some nice advantages there

e.g. their REPL is comint based, unlike our custom REPL

and is way nicer

and images are displayed in the REPL

obviously we can do both these things, but we never found the time to do so

@malabarba: The problem is that you can’t really check the version this way

as the middleware will blow up before you can evaluate any code...

frankly I don’t remember what exactly happens on 1.6, but I remember it wasn’t pretty

I don't code a lot of Racket, but when I have I've used DrRacket. In Emacs, I found quack to be the easiest to set up.

Quack also works with a lot of other schemes, which can be nice.

I was hacking a lot in Chicken Scheme for a while, and quack was pretty usable for that.

@bozhidar: are you asking what happens when the version is not supported?

on 1.6 it is the following

I've got it working so that it looks like the following:

@nkraft: thanks for the suggestion, but I found quack and it did not actually add much, so for now it is disabled, in favor of geiser, but maybe I am missing something...what does it actually provide?