This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (8)
- # beginners (99)
- # boot (60)
- # cider (44)
- # cljs-dev (47)
- # cljsrn (68)
- # clojure (223)
- # clojure-art (1)
- # clojure-russia (190)
- # clojure-sg (9)
- # clojure-uk (2)
- # clojurecup (1)
- # clojurescript (59)
- # clojurex (3)
- # core-async (43)
- # core-typed (2)
- # cursive (18)
- # datavis (7)
- # datomic (16)
- # events (2)
- # funcool (3)
- # hoplon (3)
- # jobs (1)
- # lein-figwheel (10)
- # leiningen (6)
- # off-topic (1)
- # om (123)
- # onyx (57)
- # parinfer (16)
- # portland-or (2)
- # random (1)
- # re-frame (4)
- # reagent (7)
- # remote-jobs (1)
- # spacemacs (12)
I'm trying to figure out if nrepl middleware has new features that vim-fireplace should support so Emacs package changelog is not very useful
Out middleware looks useful and eventually Vim plugins should use the indentation metadata
@juhoteperi: There's no changelog specific to
cider-nrepl. Both sides of the project have their changes logged on the
You can, however, checkout the git diff on the cider-nrepl project. That should tell you which files changed or are new.
Or check recently merged PRs. Most features in cider-nrepl are initially added as PRs (even by us)
Some things I can tell you off the top of my head (that are specific to cider-nrepl): - debugger changed a lot, - print-method.clj (tough you shouldn't have to do anything specific to support this) - track_state.clj - out.clj - The inspector does paginaton - the refresh middleware changed a bit too
I'd be interested to know if the new print-methods work in Fireplace out-of-the-box
I wonder what would be the correct place to require it? In Fireplace code or in Lein/Boot profile?
In cider we have it in the
:requires of the namespace that activates the middleware
In Fireplace there is not any code which activates the middleware, instead user needs to add it to profile plugins
Is it possible to make
cider-interrupt interrupt a Process running on the main thread created by ProcessBuilder?
To be interruptible by cider-interrupt it needs to be running under an eval session managed by
@sdegutis: See, for instance, the
with-interruptible-eval macro in
Hmm. So then I probably just need to join my ProcessBuilder's Process to the current thread immediately after starting it.
@bozhidar: And other cider devs -- congratulations on the 0.10.0 release... The debugger is awesome!!
@malabarba: it doesn't seem to make a difference for me... I think my overlays were fontlocking before setting that
@rickmoynihan yeah, the debugger overlays are always font locked. That variable is for regular evaluation overlays, like with C-x C-e.