This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-04
Channels
- # announcements (5)
- # beginners (205)
- # calva (1)
- # cider (48)
- # cljs-dev (9)
- # clojure (123)
- # clojure-berlin (1)
- # clojure-europe (2)
- # clojure-italy (5)
- # clojure-nl (6)
- # clojure-russia (7)
- # clojure-serbia (1)
- # clojure-spec (8)
- # clojure-uk (33)
- # clojurescript (134)
- # cursive (5)
- # datomic (31)
- # emacs (5)
- # figwheel-main (61)
- # fulcro (10)
- # hyperfiddle (23)
- # jobs-discuss (24)
- # klipse (1)
- # lein-figwheel (3)
- # midje (5)
- # nyc (1)
- # parinfer (2)
- # pathom (14)
- # pedestal (12)
- # re-frame (46)
- # shadow-cljs (24)
- # spacemacs (1)
- # tools-deps (37)
- # vim (4)
- # yada (22)
@vemv there is a worthy discussion here too https://github.com/clojure-emacs/refactor-nrepl/issues/195
some alternative ways are outlined here to support clj/cljs/cljc without tools.analyzer
i would consider rewrite this feature in cider itself if it is based on different stuff than the one in cljr
an other alternative to write a minimalist analyzer/parser specialised for cider needs
started such a thing but did not get far (see bug’s comment above about time… :/) https://github.com/benedekfazekas/utini
either way (tools.analyzer, jvm.tools.analyzer or homegrown analyzer) it is a big endeavour but surely a very interesting one
Thanks much for the reply! I see. Just make sure, using the cljs compiler itself is not an option, right? Why not? I guess it either doesn't ever produce the necessary info, or it doesn't provide it in a good way right?
the problem is that the AST produced this way is different than the AST produced by tools.analyzer
this is a good summary of analyzers… confusing landscape… https://github.com/clojure-emacs/refactor-nrepl/issues/195#issuecomment-294373583
> i may be wrong here but using jvm.tools.anayzer is basically that Got it! Seems likely > the problem is that the AST produced this way is different than the AST produced by tools.analyzer The problem being, clj-refactor assumes the latter format, perhaps?
not 100% sure it was merged but maybe it was. and then the above is not true anymore.. maybe...
Very nice! With that in mind jvm.t.analyzer should be a promising approach right? I see no commits since 2017 (1 year before your link), so perhaps some adaptation work is needed
maybe but as expez tells me in the refactor-nrepl github issue jvm.t.analyzer is just a thin wrapper so perhaps it does not need much work even if the stuff it depends on changes
Nice. I'll try to play around with j.t.a + the cljs compiler + refactor-nrepl if that sounds like a good plan
just to add one more idea (sorry) cider has many features that only work if the code is loaded in the REPL cider is connected to. probably find usages for loaded code only would much simpler to achieve and would still be quite valuable…
just checking in to say that my issue with the *cider-error*
buffer was indeed fixed with display-buffer-alist
Good morning. Can anyone tell me how cider-connect
auto-detects the port number chosen by lein repl
? I'm working with an in-house script that tries to do what lein repl
does, and it starts the REPL correctly, but cider-connect
port detection does not work.
It’s more than this - cider also parses the output of ps
and extracts some port information for there.
Had an interesting idea today. Inspired by a tool I saw a while ago. If functions were annotated with metadata, they could be identified as dev helpers automatically. Emacs could render a buffer with buttons to call reset, generate-data, etc. Further extensions could define simple inputs (or use spec?) to allow for prompting for input, and perhaps also delegating to an nrebl-alike for rendering results in tables.
What was the inspiring tool? Assuming you also mean vars. And is this effectively like in repl/editor binstubs?
Something that bothers me about tools.deps is the lack of consistency it brings, with regards to build tooling.
what’s the way with the latest cider to force it run something in repl once jack-in… you know via settings in .dir-locals.el
cider-connected-hook is a variable defined in 'cider.el'.
Its value is (cljr--init-middleware)
hmm… still not clear what content of .dir-locals.el
should be?
((nil
(cider-connected-hook . "???")))
basically I’m looking for a new way of setting up what’s used to be cider-cljs-lein-repl
var