This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (79)
- # boot (24)
- # cider (5)
- # clara (5)
- # cljs-experience (5)
- # clojure (126)
- # clojure-greece (5)
- # clojure-italy (3)
- # clojure-losangeles (1)
- # clojure-russia (1)
- # clojure-spec (21)
- # clojure-uk (31)
- # clojurescript (151)
- # community-development (20)
- # cursive (25)
- # datomic (24)
- # flambo (1)
- # fulcro (312)
- # graphql (10)
- # hoplon (20)
- # juxt (2)
- # keechma (6)
- # leiningen (7)
- # luminus (4)
- # om (4)
- # onyx (7)
- # parinfer (24)
- # protorepl (1)
- # re-frame (7)
- # reagent (13)
- # shadow-cljs (19)
- # spacemacs (14)
- # specter (14)
- # uncomplicate (22)
- # unrepl (1)
It doesn't seem like the dependency is enough to override the source-paths configuration, it still creates a separate sources root submodule
We have 3 projects in one git repo, client, server, and specs. Rather than constantly releasing versions of the spec project, we want to specify
:source-paths ["../specs/src"] so that the project always uses the current version of specs when building
If you’re all using Cursive, you don’t need to change the versions of the spec project. Just add a dependency on the spec project, and Cursive will set up a module dependency, which will allow the depending modules to access its source.
You can configure the profiles that are used to sync the project in the Leiningen toolwindow, the profiles that are selected in the profiles tree.
@carocad There are a couple of issues about private fn completion: https://github.com/cursive-ide/cursive/issues/1449 and https://github.com/cursive-ide/cursive/issues/1643
I think I found a bug: in a test directory, use
New -> Clojure Namespace, select
ClojureScript test, you get a
your-test.cljs file with this:
Note "clojure.test" instead of "cljs.test"
(ns app.your-test (:require [clojure.test :refer :all]))
Should be working fine. Cljs compiler aliases
clojure for simpler cross-platform code.
@cfleming greetings, I found an issue with clojure code debugger, do I report it within cursive project, or is it 3rd-party for you?
set any breakpoint inside
clojure.pprint/print-table, and then try to step over:
print-table defined inside separate file via:
IDEA highlights correct line inside wrong file: jar/clojure/pprint.clj, instead of jar/clojure/pprint/print-table.clj
(in-ns 'clojure.pprint) (defn print-table
@cfleming Is it possible to mess with how Clojure formats vectors across lines? I would like
[foo bar\n----baz] rather than
[foo bar\nbaz] if that makes sense? I had a look at the Clojure code style parameters and couldn't see anything so I'm guessing not, but never hurts to ask right? 🙂
Has anyone seen Visual Studio’s purported Clojure support? Anyone used it? A new-to-clojure-dev just asked for my help therein and it looked hella messed up. Instead of engaging in a Vim/Emacs/Cursive editor war with them, I’m trying to understand what the benefits of it over Cursive are before telling them to come to the light…etc.
clojure.test not get mapped to
cljs.test with this: http://blog.fikesfarm.com/posts/2016-07-03-clojurescript-clojure-namespace-aliasing.html?
@sandbags No, but if you can create an issue with the behaviour you’d like I’ll look at it.
@amann I haven’t, no - my impression is that it’s pretty green, but I think someone is working on it actively.
I don’t know much about it - my impression is that in general Atom would be a better choice just because of proto-REPL