This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-31
Channels
- # architecture (1)
- # aws (23)
- # beginners (13)
- # boot (18)
- # cider (5)
- # clara (1)
- # cljs-dev (22)
- # cljsjs (9)
- # cljsrn (28)
- # clojure (120)
- # clojure-canada (12)
- # clojure-dev (6)
- # clojure-italy (4)
- # clojure-korea (1)
- # clojure-russia (18)
- # clojure-sg (8)
- # clojure-spec (45)
- # clojure-uk (12)
- # clojurescript (240)
- # component (4)
- # cursive (17)
- # datomic (91)
- # editors-rus (4)
- # figwheel (2)
- # flambo (6)
- # hoplon (163)
- # instaparse (6)
- # jobs (1)
- # leiningen (2)
- # luminus (5)
- # om (22)
- # om-next (2)
- # onyx (35)
- # perun (15)
- # play-clj (1)
- # protorepl (4)
- # re-frame (106)
- # reagent (4)
- # ring (106)
- # schema (1)
- # spacemacs (17)
- # untangled (40)
- # yada (14)
@cfleming: yes that works. So do the keyboard shortcuts. But still no button. It's not a big issue. Just curious what causes the buttons to disappear.
@cfleming and now I see them! when I flipped open my laptop this morning, they were there. as if they grew overnight.
@moizsj We can just blame cosmic rays for that one: https://en.wikipedia.org/wiki/Soft_error#Cosmic_rays_creating_energetic_neutrons_and_protons
What might be an issue when in cljs figwheel repl, I try to Load file in REPL
I always get an error like java.lang.IllegalArgumentException: Namespace <ns> does not exist
, with <ns>
being always some required ns from my project (not library ns)
in case someone wondered, had to add src/cljs
into clojure (not cljsbuild) source-paths
. I guess this wasn’t needed before last update of Cursive? not sure tho
So, I’ve set up a namespace in my project and a command so that I can copy a stack trace out of a terminal window and have it show up as an io.aviso/pretty formatted exception in the REPL. It would be cool if that was built into Cursive.
@hlship: IntelliJ actually has an Analyze Stacktrace action, but I’m not sure what it does. I’ll investigate it.
I’m not sure how extensible that is, i.e. if for Clojure stacktraces I could reformat them using pretty.
Does pretty contain functionality to parse stacktraces from text? I guess usually it formats from the exception object itself.
Yes, I have some pretty usable code that does the parse. It’s all too easy to get tripped up, but for any exceptions I’ve gotten out of our application logs, it works fine.