This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-01
Channels
- # admin-announcements (8)
- # arachne (11)
- # beginners (17)
- # boot (64)
- # cider (26)
- # cljs-dev (7)
- # cljsrn (1)
- # clojure (115)
- # clojure-belgium (2)
- # clojure-dusseldorf (15)
- # clojure-poland (15)
- # clojure-russia (62)
- # clojure-spec (86)
- # clojure-uk (208)
- # clojurescript (36)
- # cursive (4)
- # datavis (11)
- # datomic (44)
- # editors (9)
- # hoplon (21)
- # jobs (4)
- # mount (21)
- # off-topic (3)
- # om (113)
- # onyx (65)
- # parinfer (2)
- # perun (3)
- # proton (6)
- # re-frame (29)
- # reagent (20)
- # yada (3)
@shader thanks! this is what I came up with
(defun ccann/forward-clj-def nil
(interactive)
(search-forward-regexp "\n([s/]*def[n]*")
(recenter)
(move-beginning-of-line 1))
(defun ccann/backward-clj-def nil
(interactive)
(search-backward-regexp "\n([s/]*def[n]*" nil 'noerror)
(recenter)
(next-line))
Personally I would just use C-M-f
and C-M-b
, which jump between top-level forms (presuming that you’re at the top level; you can iterate C-M-u
or C-M-n
to get there).
There almost assuredly are; I can’t imagine a paren-managing plugin without structural navigation keybindings.
I reference http://danmidwood.com/content/2014/11/21/animated-paredit.html for Paredit.
Nice link 😆
any ideas why we might be seeing "error in process sentinel: nrepl-server-sentinel: Could not start nREPL server: The system cannot find the path specified."?
@otfrom: I have a key binding that dumps (expectations/run-tests [*ns*])
into the REPL for that.
@otfrom there's an open issue for that. Clojure.test exposes a pretty generic API (which Cider fully supports), but expectations simply don't use it.
If someone added support for that in expectations, it would immediately work with the cider commands.
Until then, we're limited to solutions like @seancorfield's
@shader: C-c C-k loads a file. There's a menu bar listing most eval commands and the or keybinds.
@shader: You may find https://github.com/clojure-emacs/cider/blob/master/doc/cider-refcard.pdf illuminating.
@malabarba: Where would I go (in the CIDER code) to find the clojure.test
API elements that CIDER leverages? I’d be happy to submit a PR to Jay for Expectations to expose appropriate functionality.
Just bear in mind that Expectations gensyms the function names so you can’t just run a single test function 🙂