This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-08
Channels
- # atlanta-clojurians (1)
- # beginners (116)
- # cider (70)
- # cljs-dev (11)
- # cljsrn (2)
- # clojure (218)
- # clojure-italy (7)
- # clojure-nl (14)
- # clojure-nlp (11)
- # clojure-spec (8)
- # clojure-uk (113)
- # clojurescript (86)
- # core-async (14)
- # cursive (24)
- # datomic (64)
- # duct (1)
- # emacs (3)
- # fulcro (20)
- # graphql (10)
- # jobs-rus (1)
- # london-clojurians (1)
- # luminus (1)
- # nyc (1)
- # off-topic (24)
- # onyx (1)
- # parinfer (1)
- # pedestal (14)
- # portkey (11)
- # re-frame (36)
- # reagent (9)
- # reitit (5)
- # ring (1)
- # shadow-cljs (197)
- # spacemacs (21)
- # specter (22)
- # sql (15)
- # tools-deps (5)
any ideas why auto-formatting my code would break
#?(:clj [fulcro.client.dom-server :as dom])
turning it into #?(:clj)
[fulcro.client.dom-server :as dom]
?In scala, Java, or Typescript Intellij will show the parameter name when the function is called
Is there any way to resolve macro generated symbols, which are not corresponding to existing patterns? I want to use something like this, but the warnings are driving me crazy.
(defaction my-action
:contexts [a b]
:parameters [c d]
(do-something-with a b c d)
are there any options for getting a tool window (terminal, run-command, etc) to support paredit?
the higher-level problem is I have a repl via a socket or pipe (stdin/out) but I want to use it from cursive with parediting
does focus fail to return to the editor after closing the REPL window for anyone else? i.e. with the “REPL” action bound to a key my cursor winds up nowhere when i use i to close the window. hitting escape works fine to return focus to the editor (but REPL window then stays open)
Omg yes I am getting this too. After using an action dialog (like double shift or control -a or anything like that) I’ll get a zombie focus where no cursor appears and it doesn’t seem to receive modifier key presses but some things (arrow keys) act like the cursor is still there
Here are some related-looking issues: https://youtrack.jetbrains.com/issue/IDEA-192721 https://youtrack.jetbrains.com/issue/IDEA-181590
That first one cites comments in the 2018.1.4 release blog post, which said that downgrading to 2018.1.3 fixed the problem.
Might be worth trying @U09R86PA4 @U0HM5MJ5V
Here’s a similar bug saying that it’s fixed in the 2018.2 EAP: https://youtrack.jetbrains.com/issue/IDEA-181590
@U09R86PA4 @U0567Q30W issue is still there in 2018.2 EAP and 2018.1.3 for me on the mac. i’ve tried swapping in various other JDKs with 2018.1.4 as well with no luck
@U0HM5MJ5V Ok, it might be worth filing a YouTrack issue then.
@U0HM5MJ5V @U09R86PA4 Could this be your issue? https://youtrack.jetbrains.com/issue/IDEA-191839 It’s reported fixed in 2018.1.5, out now.
hmm, i’m not getting the behavior described. e.g. when the focus is lost keyboard navigation doesn’t work
i’ve had this type of issue before and it was eventually fixed by jetbrains i believe