This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-31
Channels
- # announcements (8)
- # babashka (8)
- # beginners (13)
- # biff (1)
- # calva (1)
- # cider (12)
- # clj-kondo (16)
- # cljs-dev (3)
- # cljsrn (14)
- # clojure (18)
- # clojure-austin (2)
- # clojure-czech (3)
- # clojure-europe (54)
- # clojure-germany (5)
- # clojure-nl (1)
- # clojure-norway (2)
- # clojure-spec (4)
- # clojure-survey (2)
- # clojure-uk (1)
- # clojured (15)
- # clojurescript (5)
- # conjure (6)
- # core-async (65)
- # cursive (24)
- # data-science (1)
- # emacs (9)
- # events (3)
- # graphql (5)
- # integrant (6)
- # jobs (2)
- # joyride (62)
- # lsp (5)
- # malli (10)
- # off-topic (20)
- # pathom (57)
- # polylith (18)
- # re-frame (12)
- # remote-jobs (3)
- # rewrite-clj (14)
- # sci (2)
- # shadow-cljs (41)
- # sql (9)
- # tools-deps (68)
@cfleming I was thinking would it be feasible to treat paths of :local/root
deps (direct and transitive alike) that resolve to within the intellij project as source roots as opposed to library roots?
left a bit more detail on https://github.com/cursive-ide/cursive/issues/2554#issuecomment-1141009961 about it
@U08BJGV6E I commented over there - I’m instinctively reluctant, but I haven’t really thought it through.
Every time I go back to that issue I have to refresh my memory of how Polylith works, so it takes me a while to get back into it. Real world cache invalidation!
Thanks for that. My suggestion isn't polylith-specific, really (I'd prefer a general solution anyway). I'll review what you wrote there and see if I can support the idea a bit more. This should solve the polylith problem in a general way I think.
I've added a new demo case there that isn't polylith and could benefit from the same change.
@U08BJGV6E I'm super busy with non-work stuff, I haven't had a chance to think it through, sorry. I'll definitely look at it, though.
No worries and thanks for replying. I just didn't want it to be forgotten 🙂 Do you mind if I check back in a few weeks if there isn't any activity on it by then?
Hey @U08BJGV6E, no I haven't, but I haven't forgotten about it either!
quick question/comment: i think i found a bug in the way that the cursive repl outputs long strings that have a backslash following by the letter n
: here's my input form:
{:path "C:\\some-really-long-path\\that-would-make-the-string-wrap\\and-is-followed-by-a-part-that-starts-with-the-letter-n\\new.txt"}
but the output when evaluated looks like this:
{:path "C:\\some-really-long-path\\that-would-make-the-string-wrap\\and-is-followed-by-a-part-that-starts-with-the-letter-n\
ew.txt"}
I think it has to do with line wrapping - strings over 120 characters exhibit the bug, but strings under that length do not
Hmm... it doesn't do it if Split and align multi-line strings
isn't checked... Not sure if that's a Cursive thing or not - this is under the Languages & Frameworks -> Clojure section in Preferences