CIDER finally can do M-x cider https://github.com/clojure-emacs/cider/commit/eea7e6e1402d4640f1515177a48ca0fefea18ca4 … Great success! 😄

Hey folks, quick question about cider’s cider-font-lock-dynamically option. It seems that the only way to enable the extended faces for functions et al is to evaluate the file in emacs first? I’m curious if anyone has any other approaches (like evaluating the file in a hook when you open it).

Thanks in advance!

Yeah, you have to eval the file first because this generates some extra data for the clojure-mode’s font-locking. That’s why it’s called dynamic. 🙂

You can eval files on opening them, but you should be wary of the side effects.

yeah, that’s a recipe for unpleasantness most likely 🙂

ok thanks mate

Now that we have 7 (!!!) interactive commands to do jack-in/connect, I felt it’d be nice to group those together somehow so people won’t have to remember all of them (and their keybindings). I’m still pondering whether leave this as a simple list of commands you can just from or to make it a bit more user friendly (show explanations what a command doesn instead of its name).

(I had started typing this with my message about M-x cider, but I forgot to press ENTER and I switched to another device :D)

i sure wish that elisp had clojure-style reader comments (aka, #_(defn foo ...)

You can always suggest on the Emacs Dev mailing list. I think implementing this won’t be hard, provided the core devs are interested in working on it.

need some emacs help to debug a problem: basically when I am in a cljs REPL and type (, emacs seems to hang

I have to C-g...then typing resumes normally

how can I know which functions are invoked for a buffer?

I don’t know of a nice way to do that, have you tried using the profiler (https://www.gnu.org/software/emacs/manual/html_node/elisp/Profiling.html) to narrow down the list of functions? Unfortunately they aren’t buffer specific but they could show you what functions are being invoked after you start the profiler and which ones are chewing through RAM/CPU cycles.

I tried to use that, but it seems that because I am doing C-g...I cannot really get a report

if the first character in a CLJS buffer is a parenthesis, then it hangs

you want to use the profiler

yeah I am trying that see above...it seems not to work

moving this to #emacs because it seems not related to cider

they’re probably gonna mention the profiler again in there :rolling_on_the_floor_laughing: