This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-21
Channels
- # announcements (2)
- # aws (1)
- # beginners (172)
- # boot (3)
- # calva (19)
- # cider (18)
- # clj-kondo (5)
- # cljsrn (18)
- # clojure (47)
- # clojure-europe (9)
- # clojure-finland (7)
- # clojure-italy (3)
- # clojure-nl (15)
- # clojure-spec (20)
- # clojure-sweden (2)
- # clojure-uk (72)
- # clojurescript (45)
- # cursive (42)
- # datomic (6)
- # duct (4)
- # emacs (4)
- # expound (48)
- # figwheel-main (7)
- # fulcro (64)
- # graphql (8)
- # hoplon (9)
- # hyperfiddle (1)
- # jackdaw (8)
- # jobs (4)
- # jobs-discuss (61)
- # klipse (5)
- # leiningen (6)
- # off-topic (72)
- # pathom (2)
- # planck (11)
- # re-frame (1)
- # reagent (3)
- # reitit (16)
- # remote-jobs (17)
- # ring-swagger (3)
- # shadow-cljs (49)
- # spacemacs (12)
- # sql (3)
- # tools-deps (124)
- # vim (64)
- # xtdb (4)
@cfleming Ahh, cool. It works. The trick is, you have to make a change to the file. Then it lets you select the "Only VCS Changed Text" selection. The key aspect is that this choice appears to be "sticky", so it starts behaving that way.
For those curious, the above is accessed via the Code > Show Reformat File Dialog menu
Has anyone had this issue where syntax checker is messed up when opening more than one clojure projects concurrently?
@tap yes, that’s https://github.com/cursive-ide/cursive/issues/2173. It’s not clear yet whether it’s a bug in Cursive or in IntelliJ - the corresponding platform bug is https://youtrack.jetbrains.com/issue/IDEA-211736.
@tap Oh, great. Can you check your project view, and see if everything looks ok? i.e all your modules and libraries are there?
One thing I found is when I open the second project, the first project start indexing as well.
Hmm, it happens only when I open a project that I didn't open recently. The projects that have the issue, after restart, the issue disappear. I remember the issue reappear at some point. I'll pay attention to that next time.
@tap Ok - when you get the issue again, could you try refreshing your lein projects in the lein toolwindow, and see if that fixes the problem?
FWIW, I experienced the same problem today and refreshing Leiningen projects fixed the issue for me. On the other hand, it seems to happen quite frequently with the project I'm currently working on, and sometimes making any change to the ClojureScript file fixes symbol resolution. :man-shrugging:
@cfleming No, that doesn't fix the problem. Neither refreshing from lein toolwindow nor right-click on project.clj and "Refresh Leiningen Projects"
I get a feeling that I reappear often though. Maybe after cursive update and/or IntelliJ update. I can't make it happen now.
Yeah, it only seems to happen on IntelliJ 2019.1, but that doesn’t mean it’s an IntelliJ bug - something may have changed which has provoked a bug in Cursive.
Any chance we’ll get decent keyword rename refactoring soon? Currently I’m adopting the following rule: New Rule: always prefer
(let [{:keys [::a/b]}] ...)
over
(let [{::a/keys [b]}] ...)
The former can handle kw renames via refactoring tools, the latter cannot. I’ve lost like 4-5 hours this week trying to keep things organized…and that kills me every timedoes anyone else have a problem with autocomplete and source lookup when using deps+shadowcljs+npm
instead of autocomplete showing me results from cljs, it shows me results from compiled js
@tony.kay I’m definitely interested in cases where the current rename refactoring doesn’t work. I wasn’t aware that some of them don’t.
yeah, I’m writing Fulcro 3 and spec’ing a lot of things…but heavy refactoring is a continuous need…and renaming spec keywords (or moving them to new nses when I start out with ::kw
) does not work well
this one is a real bear:
(let [{::keys [a b]} something] ...)
;; to: I move a to diff ns, which would need to end up liek this:
(let [{::other/keys [a] ::keys [b]} something] ...)
@roklenarcic That’s probably because you have a CLJS output directory which hasn’t been excluded. Cursive tries to do that automatically, but may not understand Shadow’s output dir locations.
Excluded in deps.edn or somewhere in cursive settings?
There's also the thing that all my clj, cljc files are yellow all over the clojure.core functions, but cljs files are not. Cursive seems to not be able to recognize clojure.core functions in my clj files
The deps file isn't my own, it was generated by lein new fulcro
I just ran "New -> Project from existing sources"
@roklenarcic The symbol resolution problem might be this one: https://groups.google.com/d/msg/cursive/m2QzxhCMk7I/D3l2tTokAQAJ
Re: the exclusion, hopefully you can figure out where the compiled JS is being stored - you might be able to do this by accepting one of the erroneous completions and then navigating to the result. Once you have the JS file open, then use Navigate | Select in… to open the file in the project view. There you’ll be able to see which directory that’s being stored under, and then you can right click | Mark directory as… | Excluded.