This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-20
Channels
- # announcements (1)
- # babashka (74)
- # beginners (84)
- # bristol-clojurians (3)
- # cider (2)
- # clara (14)
- # cljdoc (18)
- # cljsrn (7)
- # clojure (29)
- # clojure-australia (4)
- # clojure-europe (34)
- # clojure-italy (3)
- # clojure-nl (5)
- # clojure-seattle (1)
- # clojure-uk (33)
- # clojuredesign-podcast (2)
- # clojurescript (33)
- # code-reviews (17)
- # core-async (10)
- # cursive (8)
- # datomic (21)
- # depstar (45)
- # dirac (4)
- # duct (10)
- # emacs (1)
- # fulcro (8)
- # jackdaw (2)
- # jobs (1)
- # kaocha (11)
- # leiningen (2)
- # off-topic (8)
- # pathom (35)
- # pedestal (3)
- # protorepl (13)
- # rdf (39)
- # re-frame (23)
- # reagent (2)
- # releases (1)
- # remote-jobs (6)
- # reveal (2)
- # rewrite-clj (18)
- # shadow-cljs (51)
- # sim-testing (2)
- # spacemacs (2)
- # tools-deps (37)
Is there a way to configure proto-repl to give me more info about syntax errors when reloading?
As a general point, I'd recommend not using any of the auto-refresh/auto-reload stuff. It can get your REPL into a weird state and it's hard to recover. Much better to develop a workflow where you eval every top-level form as you make changes, so that it becomes second nature.
I was starting to worry that protorepl was abandoned. I'm still very new to using RDD. Do you switch to the namespace of a function you're working on for that namespace? It seems like the general guidance is to do RDD in a namespace that isn't part of application code. I see people create a file and define a user namespace a lot. I'm still unclear as to how to develop/modify functions via RDD that exist in a defined namespace.
I use "Rich Comment Forms" -- code inside
(comment
<scratch code goes here>
,)
then it's in the context of your actual code (can call your functions) and it can stay in the file as a record of how you developed your solution.Rich Hickey uses that approach -- you'll see RCFs at the end of several Clojure files in the core libraries -- and Stu Halloway and others also advocate using comment
forms to hold scratch code as you're exploring the solution.
Never type into the REPL directly: always write code and eval it -- that's it in a nutshell.
Since you're working in a source file, nearly all Clojure integrations for editors take care of evaluating the code in the correct namespace automatically, so you never need to worry about that.
BTW, the Chlorine package for Atom doesn't even have a REPL "input" area: so it forces you to always write code and eval it. But you'll normally start a REPL yourself from a terminal, with a Socket REPL running, and you can still type into that if you really feel the urge to just try out an expression without putting it in source code.
I have a couple of videos on YouTube showing my Chlorine/Atom workflow https://www.youtube.com/channel/UC8GD-smsEvNyRd3EZ8oeSrA -- in those videos I'm also using Cognitect's REBL data browser but I've switched to Reveal now so I really need to do some updated videos.
Thank you! This is most helpful. Going to try chlorine and the rich comment workflow right now. I had already gotten used to writing forms and sending them to the repl with protorepl which was quite a revelation.
I need to brush up on the history of all these different repls at some point.
The #chlorine channel nearly always has some folks who can help you, if you get stuck.
As for getting more info about the error from ProtoREPL, probably not? ProtoREPL has pretty much been abandoned (unless there's been new activity recently). All the Atom users have switched to #chlorine now, which is very well maintained @skinner89