Fork me on GitHub
#cider
<
2015-07-08
>
alejandro01:07:09

how does cider-jack-in decide whether to use lein or boot?

bostonaholic02:07:54

@alejandro: it looks for either a project.clj or a build.boot

bostonaholic02:07:25

if both exist, it asks the user

alejandro02:07:24

cool, thanks!

bostonaholic02:07:02

for questions like that, I simply read the source to find out

bostonaholic02:07:10

HUGE benefit of OSS

bostonaholic02:07:02

and if you don't know where to look in github, here's my process for finding your answer 1. M-x find-function cider-jack-in 2. I saw project-type in a let binding which was being bound from a cider-project-type function call 3. follow to definition of cider-project-type and voilá, 2-3 lines in I can see how it determines to use lein or boot

aengelberg04:07:23

Until now I thought all hope was lost getting cider 0.9.1 to work.

bozhidar06:07:41

@aengelberg: unfortunately, the upgrade turned out to be more complicated for most people that I thought it’d be. At least, now there are enough resources around to help people with such issues.

seancorfield06:07:22

Wow, makes me glad I’m using Emacs Live… It’s been almost seamless, all things considered… simple_smile

jrychter07:07:28

re boot vs lein — just as a data point, we tried moving to boot and are now moving some projects back. There is no single "superior" build tool, each has its merits.

rickmoynihan09:07:46

does anyone else have problems with cider-debug rendering the overlays in the wrong place, and not highlighting the current expression properly? M-x cider-version 0.9.1

malabarba09:07:44

@rickmoynihan: It's not a known bug. Could you give an example of when that happens?

rickmoynihan09:07:18

@malabarba: I dunno I think it might happen when a value prints to more than one line

rickmoynihan09:07:37

but it doesn't seem to recover

rickmoynihan09:07:42

so might not be that

rickmoynihan09:07:34

also the overlay doesn't appear to scrub properly when its done

rickmoynihan09:07:07

and it appears to trigger a window split

malabarba09:07:33

Ok, I'll look into it. It's probably just a bug in the 0.9.1 logic

malabarba09:07:16

I mean, it's obviously bug, simple_smile but probably unrelated to the print method or incanter

malabarba10:07:58

@rickmoynihan: Ok, I've found the issue. Seems to be a general thing with multiple-arity functions (embarassing). It was incidentally fixed on the 0.10.0 snapshot release.

malabarba10:07:21

But I'll see whether we can have a 0.9.2 bugfix release. Depends on how close or far 0.10 is, I suppose.

bozhidar11:07:56

there won’t be a 0.9.2 release

bozhidar11:07:14

my current plan is to do 0.10 around the end of the month

bozhidar11:07:25

mostly because of all the debugger improvements

bozhidar11:07:32

maybe even a bit earlier

bozhidar12:07:00

to put it in simpler terms - the moment the debugger is working well with cljs we’ll be good to release 0.10

rickmoynihan13:07:09

@malabarba: @bozhidar: great... thanks guys

agile_geek13:07:57

@bozhidar: so when are you going to bump it to 1.0.0? Someone from Java world asked me why a lot of Clojure libraries are on 0.x minor versions and never seem to commit to a major release. It sends a message that libraries not ready for ‘production’ yet. I know in this case we are talking about an elisp package not Clojure but you get my point.

bozhidar13:07:34

I’ve said this a few times over the year, but my plan is to release 1.0 when we reach feature parity with SLIME

bozhidar13:07:11

right now the only big missing pieces are things like find-usages, rename-symbol, etc (AST based stuff)

bozhidar13:07:23

those actually never worked properly in SLIME, but still

bozhidar13:07:13

we’re working with @benedek & co to bring this functionality from clj-refactor into cider itself

bozhidar13:07:36

I hope this will happen before the conj, but who knows...

bozhidar13:07:05

I’m mostly happy we’re constantly making progress

bozhidar13:07:18

and I don’t care that much about a magical version number

bozhidar13:07:41

but I’ll definitely be very happy if I get to push the 1.0 release eventually

mitchelkuijpers14:07:19

Does anyone know how to make clj-refactor behave with src/clj and src/cljs?

agile_geek14:07:49

@mitchelkuijpers: I would ask @benedek

benedek14:07:13

hi @mitchelkuijpers can you be a bit more specific? which feature do you have problems with with this setup?

mitchelkuijpers14:07:49

When I create new file it creates a namespace like

clj.my-namespace.handler

mitchelkuijpers14:07:58

this is a bit annyong but not that bad

mitchelkuijpers14:07:43

but when i try the rename-file-or-directory command I get an error like this:

cljr--maybe-rethrow-error: Can't find src dir prefix for path /users/mitkuijp/development/relations_for_jira/src/clj/relations_for_jira/companies/companies.clj

mitchelkuijpers14:07:10

Is there an option I can set or something?

benedek14:07:57

what kind of repl do you have running?

benedek15:07:02

sry got distracted

benedek15:07:31

as for the autonamespace declaration: that is a function in clojure mode (https://github.com/clojure-emacs/clojure-mode)

benedek15:07:04

you can easily opt out with (setq clj-add-ns-to-blank-clj-files nil) if you want to. not sure if you can configure clojure mode itself to get it right for your setup.. \\cc @bozhidar

mitchelkuijpers15:07:01

Would it help if I changed to src/ and src-clj instead of scr/clj src/cljs ?

benedek15:07:00

i think the second one might be bug. can you perhaps post your project.clj (if you use leingingen)?

mitchelkuijpers15:07:04

with some leinigen so my colleague his intellij works one moment please

mitchelkuijpers15:07:26

(defproject relations-for-jira "0.1.0-SNAPSHOT"
  :dependencies [[org.clojure/clojure "1.7.0"     :scope "provided"]
                 [adzerk/boot-cljs      "0.0-2814-4" :scope "test"]
                 [adzerk/boot-reload    "0.3.1"      :scope "test"]
                 [danielsz/boot-environ "0.0.3" :scope "test"]

                 ;; server
                 [environ"1.0.0"]
                 [org.danielsz/system "0.1.8"]
                 [aleph "0.4.0"]
                 [yada "0.4.3"]
                 [org.clojure/tools.nrepl "0.2.10"]
                 [cheshire "5.5.0"]
                 [enlive "1.1.5"]

                                        ; Datomic
                 [com.datomic/datomic-pro "0.9.5067" :exclusions [[org.slf4j/slf4j-nop]
                                                                  [org.slf4j/slf4j-log4j12]]]
                                        ; Datomic schema management
                 [io.rkn/conformity "0.3.5"]

                                        ; logging
                 [org.clojure/tools.logging "0.3.1"]
                 [ch.qos.logback/logback-classic "1.1.3"]

                 ;; json web token
                 [clj-jwt "0.0.13"]
                 [pandect "0.5.2"]
                 [buddy "0.5.5"]

                 ;; client
                 [org.clojure/clojurescript "0.0-3308" :scope "provided"]
                 [cljs-ajax "0.3.13" :scope "provided" :exclusions [clj-time]]
                 [secretary "1.2.3" :scope "provided"]
                 [re-frame "0.4.1" :exclusions [[org.clojure/clojurescript]
                                                [org.clojure/clojure]] :scope "provided"]]
  :source-paths ["src/clj" "src/cljs"]
  :resource-paths ["resources"])

benedek15:07:49

i guess something goes wrong when we try to figure out the relative path

mitchelkuijpers15:07:29

Awsome thx @benedek

benedek15:07:51

np, thx for the feedback

benedek16:07:40

thx @agile_geek for conjuring me 😉

agile_geek16:07:04

@benedek my pleasure. Although I think I just gave you work to do. ;-)