I've been getting this thing lately where when I try to evaluate a form all I get is a complaint in the minibuffer saying "Namespace Not Found"

Any repro steps for this?

It seems in this case it started when I created a new namespace, it's there, it's saved, it's on the filesystem in the right place. I can eval the ns form, but anything else it won't do.

load-file doesn’t work?

where would I do that? (load-file "full-path.clj") from the REPL?

tried this with two namespaces, for one doing load-file cleared the problem, for the other it doesn't. they both contain nothing but an empty (ns) form

how do I enable the thing where I can see all nREPL messages going back and forth?

nrepl-toggle-message-logging

that message is in the response. so for sure check what's going over the wire

ok this is interesting

(-->
  id         "35"
  op         "eval"
  session    "8e6e275a-6335-4ead-9e78-827b408adbd4"
  time-stamp "2018-07-24 15:07:34.188062715"
  code       "(+ 1 1)
"
  column     1
  file       "/home/arne/Nextjournal/nextjournal/journal/server/env/dev/server/figwheel/api.clj"
  line       2
  ns         "server.env.dev.server.figwheel.api"
)
(<--
  id         "35"
  session    "8e6e275a-6335-4ead-9e78-827b408adbd4"
  time-stamp "2018-07-24 15:07:34.207152917"
  status     ("namespace-not-found" "done" "error")
)

vs

(ns server.figwheel.api)

when that file was first created it automatically got an ns form that read (ns server.env.dev.server.figwheel.api) (I guess clj-refactor does that)

somehow CIDER thinks it still has that namespace, even though the ns form has been updated, and even though I restarted nREPL (!)

did you kill the buffer?

there's a buffer local version to hold that value apparently

@dpsutton I don’t think we have a buffer-local for for the source buffers.

There’s a bit of logic to watch the ns for modifications even.

reloading the buffer does clear it up

(setq-local cider-buffer-ns ns) . I'm not sure how it gets set in code buffers but there is some state out there

Interesting. Guess really some buffer-local ns var must have been set, but those were never intended to be used with source files.

yeah i've never seen that before

@plexus do you override the start ns from user to something else?

yes, we do, we have a server.repl namespace

and is this that namespace or is it unrelated?

no, that's unrelated

well i'm at a loss then. if you can give some steps to repro from a new project i can look into it but if its not worth your time i understand that as well

I'll see if it comes up again, ran into this three times in two days on three separate projects so not unlikely

Hi, just updated Cider this morning an am getting this error

@pablore You’re getting it from clj-refactor.el and refactor-nrepl (which was recently updated).

Guess you’ll have to disable it.

How do I do disable it? I’m using spacemacs

Read CIDER’s FAQ/Troubleshooting.

There was something about this there.

thanks!

@pablore I got the same error when using Java 1.10. I downgraded to java 1.8 and can still use clj-refactor.

Hey, does anyone know how to programatically evaluate something with cider and show the result in a window in Emacs? This is what I have done: http://ix.io/1igi . I think it actually works, except that I don't know how to get the output in a window in a decent way (I could insert the result into a buffer, load clojure mode and indent it, but I'm sure there's a better way). Also, what's a good resource for learning Cider internals?

@andre.peric there's the manual at https://cider.readthedocs.io/en/latest/ and i have some internal walkthroughs at http://hackingcider.com/

Thanks, hackingcider seems to be exactly what I want

awesome! when you learn things make an overview of what was useful and submit a PR!

has anyone tried hacking on clojure.spec with Cider? I can’t get it to work for some very weird reasons:

#object[clojure.spec.alpha$and_spec_impl$reify__2173 0xf14b48f
   "clojure.spec.alpha$and_spec_impl$reify__2173@f14b48f"] is not a
   fn, expected predicate fn

When loading clojure.spec.alpha it seems the c/and in line 81 is pointing to spec’s and for some reason …

I haven’t used spec much, but generally CIDER shouldn’t affect spec usage at all.

It’s not really about spec usage but rather about hacking on Spec itself — as in running cider in this repo: https://github.com/clojure/spec.alpha/

It should be a project like any other. Not sure what can special to it.

I’m also not sure what could be different which is why I came here to ask if anyone else tried it 😄

doesn't cider depend on spec in some way?

No, it doesn’t.

It does, for the spec Explorer?

https://github.com/clojure-emacs/cider-nrepl/blob/master/src/cider/nrepl/middleware/spec.clj in Orchard now

I don't think that's a dependency which is inlined though.

It’s not a project dependency at all - we check if spec is present, otherwise we just stub it.

(ns orchard.spec
  (:require [clojure.walk :as walk]
            [clojure.pprint :as pp]
            [clojure.string :as str]))

(defmacro spec [fname & args]
  `(when-let [f# (or (resolve (symbol "clojure.spec.alpha" ~fname))
                     (resolve (symbol "clojure.spec" ~fname)))]
     (f# ~@args)))

(defmacro spec-gen [fname & args]
  `(when-let [f# (or (resolve (symbol "clojure.spec.gen.alpha" ~fname))
                     (resolve (symbol "clojure.spec.gen" ~fname)))]
     (f# ~@args)))

So, there’s basically nothing to inline - if spec’s there it will be resolved, otherwise it won’t be.

Not sure how this can cause the problems @martinklepsch mentioned.

@martinklepsch I tried it with leiningen and the same error. It seems that the key setting is -Dclojure.spec.skip-macros=true: https://github.com/clojure/spec.alpha/blob/master/pom.xml#L73 With it I can at least eval the alpha namespace.