This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-26
Channels
- # admin-announcements (1)
- # beginners (12)
- # cider (2)
- # cljs-dev (6)
- # cljsrn (4)
- # clojure (123)
- # clojure-austin (10)
- # clojure-brasil (1)
- # clojure-canada (21)
- # clojure-conj (5)
- # clojure-dev (8)
- # clojure-gamedev (42)
- # clojure-russia (121)
- # clojure-sanfrancisco (2)
- # clojure-spec (25)
- # clojure-uk (36)
- # clojurescript (195)
- # clojutre (3)
- # cursive (43)
- # datomic (6)
- # defnpodcast (2)
- # dirac (14)
- # emacs (2)
- # ethereum (2)
- # events (2)
- # funcool (6)
- # hoplon (76)
- # jobs (1)
- # kekkonen (9)
- # lein-figwheel (1)
- # leiningen (4)
- # mount (6)
- # off-topic (5)
- # om (2)
- # onyx (91)
- # pedestal (2)
- # protorepl (14)
- # re-frame (22)
- # reagent (20)
- # rethinkdb (1)
- # ring (2)
- # schema (3)
- # sfcljs (3)
- # spacemacs (15)
- # specter (12)
- # testing (1)
- # yada (63)
I haven't seen keybinding issues before like that. @legatus7 can you try directly invoking the command using the command pallette?
That will determine if it's actually a keybinding problem or something else.
@carocad: pretty cool! I'm excited to see the final product and try it out.
@jasongilman yeap 🙂 I think we might even be able to have inline exceptions for every command but that would be a far update. Too many changes at once wouldn't be good jeje
BTW: do you have any idea why are we still getting those (form-init1234532.clj) things on the exceptions? it seems that proto-repl can recognize other files, but not the current file where things are executed 😕 What I mean is that if I have an error in a function which calls another function in another file, the file is correctly reported back. But if the error is in the current file where I defined the function then it fails ...
I need to look into that. It's specifying the file name to nREPL but the code block is just reported as form in the exception. I need to understand more about how Clojure stack traces are generated.
@jasongilman hey there, trivial PR waiting on proto-repl-charts (cannot be compiled on the latest alpha version of clojure because of a typo), please take a look!
Oh I think I found the reason or at least a clue. If you load the complete file that defines the functions with bugs and then call it with bad input the exception correctly reports the file where the functions where defined ! It seems that this problem only happens if you send the function definition to the repl
Oh guys that's pretty!
I so like that you get the callee highlighted, good job! Can I use this as feature request for cider? 😄
also, about stacktraces, this is a snipped to convert them to a list of strings + optional data:
(merge {:stacktraces (mapv str (.getStackTrace ex))}
(when-let [data (ex-data ex)] {:ex-data data}))
^ works for both normal exceptions and ex-info
exceptions
@moxaj: sorry I missed that. I'll merge it.
@moxaj: Merged and I fixed some other require's as well. It's proto-repl-charts "0.3.2" now