This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-21
Channels
- # announcements (9)
- # beginners (222)
- # boot (11)
- # calva (40)
- # cider (1)
- # clj-kondo (10)
- # cljs-dev (1)
- # cljsrn (8)
- # clojars (4)
- # clojure (50)
- # clojure-dev (4)
- # clojure-ecuador (1)
- # clojure-europe (4)
- # clojure-italy (3)
- # clojure-madison (2)
- # clojure-nl (26)
- # clojure-spec (86)
- # clojure-uk (34)
- # clojurescript (11)
- # clr (1)
- # cursive (46)
- # datomic (19)
- # emacs (4)
- # events (1)
- # fulcro (22)
- # graalvm (4)
- # graphql (2)
- # jobs-discuss (40)
- # leiningen (10)
- # luminus (6)
- # nrepl (7)
- # off-topic (18)
- # onyx (6)
- # overtone (1)
- # pedestal (2)
- # planck (1)
- # re-frame (5)
- # reagent (3)
- # reitit (8)
- # rewrite-clj (2)
- # shadow-cljs (139)
- # sql (4)
- # tools-deps (42)
Yeah, it’s been identified as a platform issue and JB have been able to reproduce it - it should be fixed in 2019.2 at some point, and hopefully backported to 2019.1 too.
Unfortunately 2019.x has pretty much sucked in terms of major bugs affecting Cursive.
Hey 🙂 I got an issue with Cursive and IntelliJ modules. Scanning project.clj/deps files will make Cursive set up IntelliJ modules. I got multiple clojure projects in a single IntelliJ project and they share some folders in their config files (project.clj or deps). This results in Cursive adding those shared folders as source roots in multiple modules. This isn't allowed in IntelliJ and while it seems to work behind the scenes, it leads to problems for example when editing the module config in IntelliJ: I have to remove the conflicting source folders first to be able to save the modules config, then I need to make Cursive rescan the CLJ project files which will add the source roots again behind the scenes. Same game when I need to edit modules again at any point in the future. ;( Is there a way to resolve that or a decent workaround?
@U0567Q30W any thoughts about this?
@U066HBF6J My apologies, I missed this message the first time around. When you say: > they share some folders in their config files (project.clj or deps) can you give an example of what that looks like in the project file? Are these just source roots?
Here is a repo as a minimal example https://github.com/nblumoe/cursive-source-root-conflicts
Module config cannot be changed due to having the same source root on both app modules.
I think I found a related issue and commented on it too: https://github.com/cursive-ide/cursive/issues/2078
FYI it seems that they started to work on the issue about brackets 😄 https://youtrack.jetbrains.com/issue/IDEA-211720
does anyone experience this too?: submit something to repl from repl-edit-pane, and up-arrow-key stops cycling through repl-edit-pane-history. submit something again, and up-arrow-key works again
it seems to have something to do with trailing spaces of the thing you submit. and often happens when eval results in exception
I think I saw something like that once, haven’t seen it in a while though.
I’m on IntelliJ 2019.1.3, with the latest eap Cursive, haven’t had that problem in something like a year, I’d say.
Let me try something with trailing spaces and an exception…
Still works.
:man-shrugging:
I’m on Mac OS X, what’s your system
the thing is: It seems it only happens with spaces and exceptions, but not for all spaces and not all exceptions.
Ok, interesting, just seeing what we have in common and what’s different.
Do you have an example of an exception that’s caused this for you recently?
no, but it just happened to:
Loading src/statecharts/specs.cljc... done
(nat-int? -1)
=> false
Very peculiar.
and I can't confirm were there trailing spaces or not, because cursive strips them before printing =>
:)
or does it?
It’s early morning in New Zealand, maybe leave a ping for cfleming, I expect he’ll be on in a bit.
I think it can wait for him to read this on his own schedule :) thanks for feedback, @manutter51
have an interesting behavior: select top form, move it with shortcut (e.g. cmd+shift+up): form is moved (it and a prev one switch places), but selection stays on earlier line(s): before and after "move":
@misha @manutter51 That looks like https://github.com/cursive-ide/cursive/issues/2003, which I’ve never been able to reproduce - it’s really weird.
@misha Hmm, that selection bug is a weird one indeed. Could you file an issue for that please?
I also get this sometimes but I'm not able to repro 100% of the time.