This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-17
Channels
- # beginners (52)
- # boot (116)
- # cider (21)
- # cljs-dev (44)
- # clojure (104)
- # clojure-dev (82)
- # clojure-greece (5)
- # clojure-japan (4)
- # clojure-nl (14)
- # clojure-russia (65)
- # clojure-serbia (3)
- # clojure-spec (38)
- # clojure-uk (9)
- # clojure-ukraine (1)
- # clojurescript (65)
- # clojurewest (1)
- # community-development (1)
- # core-logic (3)
- # cursive (5)
- # data-science (9)
- # datomic (13)
- # emacs (45)
- # euroclojure (1)
- # hoplon (2)
- # instaparse (23)
- # javascript (1)
- # jobs (2)
- # klipse (43)
- # leiningen (8)
- # lumo (25)
- # off-topic (7)
- # om (13)
- # om-next (3)
- # onyx (11)
- # pedestal (12)
- # planck (19)
- # proton (1)
- # re-frame (26)
- # reagent (26)
- # remote-jobs (13)
- # ring-swagger (23)
- # spacemacs (1)
- # untangled (3)
Very very interesting @moxaj
Could you open an issue on klipse with a link to your repo?
the first link in the issue references two functions in the analyzer namespaces, i'll try to debug those in the meantime
cool 😎
on a separate note, you really should give parinfer a try ^^ I see some misaligned parens in the klipse sources
I have switched to paredit recently
Where do u see misaligned parens?
in klipse.lang.clojure
for example. not sure where exactly, but the parinfer plugins warns me
maybe the indentation is not perfect?
yeah. Now it makes sense
Feel free to fix the identation...
so it should work?
but it doesnt :thinking_face:
you are right
how could it be that in klipse it is done the wrong way?
I have no idea ^^. Went through the relevant namespace, but it's a tad too complicated for me
unfortunately lumo I believe uses its own bundled cljs sources, so it won't see my patched compiler
there might be a way to make lumo use your own compiled
try to ask on #lumo
Also, if you have a standalone repro where desugar doens’t do what it should do, you could ask on #cljs-dev
Another thing, try to deactivate all the with-redefs
inside klipse
around eval-str
I feel that you are very close...
The following throws an error when evaluated in klipse and lumo as well:
(ns klipse-test.a
#?(:cljs (:require-macros [klipse-test.a])))