Clojurians
#cider
<
2018-01-30
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

xiongtx03:01:03

This only happens for .cljc files? Not .clj or .cljs?

qqq06:01:38

not sure; 99% of my code is in *.cljc files

qqq06:01:02

I'm starting to suspect it's something like the emacs message buffer getting too large over time or something else like that, i.e. some type of a mem leak

bozhidar09:01:51

:smile: :smile: :smile:

bozhidar09:01:04

Hmm, normally something like this shouldn’t be a problem. I never restart my Emacs for months at a time.

bozhidar09:01:22

You can check with the Emacs Profiler what’s going on - it’s easy to use and quite helpful.

bozhidar09:01:37

> cider-font-lock-as-clojure doesn’t use CIDER’s extra font lock rules. What’s the easiest way to make it do that?

bozhidar09:01:56

Hmm, I never thought about this to be honest. Probably you’d need to enable cider-mode in some temp buffer and evaluate the code there to get the right font-locking.

xiongtx18:01:10

I ended up making cider-var-info calls for each Var. This is slow but we only need to do build the source once (well, except for a little trickiness involving whether CIDER was jacked in or not). Unfortunately cider-var-info doesn’t return a type the way cider-apropos does, so I had to resort to some hack: https://github.com/clojure-emacs/helm-cider/blob/27a773d1477449605d463333de378531caa681da/helm-cider-util.el#L95-L101. This works :ok_hand: for most things but not for e..g multimethods, which don’t return arglists for some reason.