This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-13
Channels
- # beginners (67)
- # boot (18)
- # cider (28)
- # clara (11)
- # cljs-dev (1)
- # cljsrn (7)
- # clojure (134)
- # clojure-dev (2)
- # clojure-dusseldorf (1)
- # clojure-greece (1)
- # clojure-italy (13)
- # clojure-losangeles (2)
- # clojure-nl (2)
- # clojure-russia (2)
- # clojure-spec (2)
- # clojure-uk (52)
- # clojurebridge-ams (1)
- # clojurescript (78)
- # core-async (1)
- # core-matrix (2)
- # cursive (12)
- # data-science (22)
- # emacs (10)
- # events (1)
- # fulcro (28)
- # graphql (4)
- # hoplon (16)
- # jobs (1)
- # lein-figwheel (3)
- # leiningen (3)
- # nyc (1)
- # off-topic (19)
- # onyx (70)
- # parinfer (2)
- # pedestal (1)
- # portkey (9)
- # protorepl (2)
- # re-frame (16)
- # reagent (39)
- # ring-swagger (5)
- # rum (1)
- # schema (2)
- # shadow-cljs (216)
- # specter (5)
- # sql (1)
- # uncomplicate (4)
- # unrepl (6)
- # vim (25)
- # yada (5)
@cfleming a request on Cursive’s “read-only REPL”: please don’t mode me in while Clojure is starting up, it creates an attention dependency - I have to watch the REPL until I can paste or start typing the command I’m going to run. Instead of moding the user in, show an indicator or mute the text I’m typing so I can see the REPL isn’t up yet
@petrus There’s an issue about that: https://github.com/cursive-ide/cursive/issues/1579
Ideally I’d let the user type commands, but in the output pane show them dimmed or something to show that they haven’t been sent yet.
So then your options would be: never focus the REPL, or focus it right at the start, allow commands to be entered but not executed until the REPL is fully started.
Hi, I am using clara rules which uses macros for handling rule definitions. In this there is an implicit declaration of a variable within the rule of the format ?name this strings are always shown as not being referenced. Is the any way to either switch these warnings off or make them actually check