This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-11
Channels
- # announcements (1)
- # beginners (84)
- # boot (325)
- # cbus (1)
- # cider (13)
- # cljs-dev (1)
- # cljsjs (1)
- # cljsrn (15)
- # clojars (8)
- # clojure (221)
- # clojure-czech (2)
- # clojure-ireland (8)
- # clojure-madison (28)
- # clojure-poland (176)
- # clojure-russia (111)
- # clojurebridge (7)
- # clojurescript (75)
- # community-development (70)
- # conf-proposals (19)
- # core-async (29)
- # css (12)
- # cursive (66)
- # datavis (15)
- # datomic (61)
- # devcards (15)
- # dirac (2)
- # editors (13)
- # emacs (9)
- # funcool (7)
- # hoplon (13)
- # jobs-discuss (5)
- # ldnclj (39)
- # ldnproclodo (1)
- # lein-figwheel (3)
- # leiningen (21)
- # liberator (26)
- # off-topic (12)
- # om (153)
- # onyx (168)
- # parinfer (165)
- # proton (21)
- # quil (5)
- # re-frame (58)
- # reagent (4)
- # ring-swagger (12)
- # spacemacs (3)
- # yada (120)
I noticed that 16 EAP is out … I can’t see if it’s been asked before but when do you propose to support it?
@cfleming: Also, I was wondering if you have a timeline for the standalone version of Cursive?
Say, is there a setting or something that will let me see the full traceback when something I'm doing in the repl generates an exception?
@cfleming: In my project, I am using a macro named deftry
to define functions. How can I make cursive
aware of deftry
?
I've got a strange situation where Cursive is trying to load files that are not on my classpath
we have a demos/ directory, which is not on the classpath, with .clj files in it, and they are loaded form Gorilla REPL
and loading the .clj files in demos/ causes problems
meaning it throws a compiler exception and I can't run tests
Is there some issue existing already about syntax highlighting with alt! ? I'm seeing a binding marked as a syntax error (squiggle underlined), but evaling the code in the repl and running it works fine, just Cursive seems to think the syntax is wrong.
https://clojuredocs.org/clojure.core.async/alt! - Try the code in these examples and you'll see it highlight the bindings inside the alt as an error
more specifically, it says "cannot be resolved"
@raymcdermott: The next build should support v16
@viebel: Right now there’s no good solution for that. I’m planning a workaround soon (marking certain forms as def-like or let-like), and a long-term solution (an API for adding full support for forms)
@hugesandwich: That’s probably the same problem as @viebel’s - Cursive doesn’t automatically have support for macros which define new symbols. I’ll check those examples and add support for that.
yeah it makes sense since alt! is using macros under the hood
thanks!
@jcromartie: is the demos/ directory a source root?
no, it isn't
@cfleming: it's intentionally outside of a source directory
@jcromartie: Is the project something I can look at, or is it internal?
it's internal
no rush
I've got alternatives (running command-line REPL right now)
I think it has to do with transitive loading
when I execute "Run test under caret"
but nothing should actually depend on this file...
that's the strange part
nothing does require it
./.idea/workspace.xml: <option value="$PROJECT_DIR$/dev-system/demos/sprint44.clj" />
from grep
for the file in question
Give me a moment, I can probably send you a diagnostic tool to help figure this out.
in <component name="IdeDocumentHistory"><option name="CHANGED_PATHS"><list>...
That just means you’ve had it open in the editor, I think. Which element in that XML is that option inside?
so, Cursive thinks it should load it for some reason, and that's the only place the file name shows up anywhere
I'd guess that's part of the puzzle
but I turned off transitive loading the other day
Ok, give me a moment to check the code, and I’ll send you something to test this, hopefully in about half an hour.
because automatically loading files when running tests was causing failures due to defrecord dispatch problems
@jcromartie: When you turned off transitive loading, did that fix the problem?
@jcromartie: Also, which IntelliJ version are you running?
@cfleming: it helped earlier, but I'm not sure why it's loading a bunch of .clj files now
I'm not sure if "Run test under caret" might do something different
but at least "Run tests in current NS" stopped loading .clj files automatically
@jcromartie: Which IntelliJ and Cursive versions are you running?
let me see...
IntelliJ 15.0.2
Cursive 1.1.0-15
so the "run tests in current NS" action not loading deps might just be my imagination
gotta run for now
thanks for the help