This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # arachne (2)
- # architecture (23)
- # bangalore-clj (5)
- # beginners (35)
- # boot (79)
- # cider (6)
- # cljs-dev (34)
- # cljsrn (9)
- # clojure (164)
- # clojure-argentina (2)
- # clojure-austin (4)
- # clojure-italy (7)
- # clojure-russia (40)
- # clojure-serbia (1)
- # clojure-spec (76)
- # clojure-uk (36)
- # clojurescript (47)
- # cursive (14)
- # datascript (2)
- # datomic (8)
- # dirac (19)
- # emacs (29)
- # heroku (7)
- # hoplon (35)
- # jobs-rus (1)
- # juxt (2)
- # leiningen (1)
- # lumo (23)
- # mount (4)
- # off-topic (22)
- # om (16)
- # onyx (19)
- # parinfer (10)
- # pedestal (47)
- # proton (5)
- # re-frame (88)
- # rum (1)
- # spacemacs (33)
- # sql (29)
- # uncomplicate (1)
- # unrepl (131)
- # untangled (5)
- # yada (12)
That seems to have done the trick.
Awesome! Thanks for your hard work on this. I’m something of a emcas newbie. At this point in your instructions you type
C-c s w. For the magic debug tree.
I’m 90% sure C-c means Ctrl-C but when i git those keys spacemacs tells me there are no commands following that.
I’m afraid to emit i use spacemacs mainly by getting around helm. If i search for sayid i get a list of commands like sayid-trace-all-ns-in-dir. Which i ran before executing the tests. However im not sure what command to run after that.
which is what the code you mentioned earlier
is supposed to do
(eval-after-load 'clojure-mode '(sayid-setup-package))
but... the function those keys are meant to be bound to is
sayid-get-workspace. You should be able to call that and see what, if anything, was captured
Ah ok. let me fiddle with my setup. I just added
sayid to the
After properly adjusting my head, it was clear i just needed to add
(with-eval-after-load ‘clojure-mode (sayid-setup-package)) to my user-config in my .spacemacs file.
eval-after-load would almost certainly work to.
It seems like Sayid might conflict with some of spacemacs configuration settings.
For example if i type
i i get insert-mode (as i’m using evil mode). I’ll see if i can find the time to fiddle further. Its possible these problems are rather pedestrian in nature.
@drewverlee sayid is definitely super-cool, but at least as of his /conj talk, it was at a pretty beta stage. If you run into much trouble with it, you might want to consider working with cider for now, since that’s quite mature & well-integrated with spacemacs, and has a pretty decent debugger.
@drewverlee are you pressing
i in the sayid buffer? is that buffer in evil-mode? (I've never user spacemacs or evil)
i in insert-mode would typically just insert the letter
i. @bpiel if you can say what the name of the relevant emacs function is, @drewverlee you can hit
M-x to enter
helm-M-x mode, and then type the name of the function and it’ll tell you what keys (if any) are currently bound to that function.
depends on which sayid mode we're talking about. Assuming it's the buffer that shows the trace tree,
i should call
My guess is there’s probably some prefix he has to hit to make those bindings available.
SPC-m opens the major-mode menu, but I’m guessing sayid is a minor mode?
For clojure-mode buffers, sayid adds its keybindings through some prefix-map mechanism (something I just recently learned about). There's no mode. But, sayid has a few major modes that it uses for the different types of sayid buffers
Ah, ok. If I get a chance I’ll install it sometime in the next day or so & see if I can figure out what the commands would be in spacemacs/evil.
Quick answer (just installed) — looks like some of the sayid commands are bound behind
C-c, but there are quite a few that aren’t bound.
Ah, yeah, here we go. @drewverlee typing
C-c s (that’s ctrl-c followed by
s) will get you into a sayid menu.