Fork me on GitHub
#vim
<
2019-11-17
>
dharrigan08:11:20

Interesting!

sogaiu14:11:58

reminds me a bit of douglas crockford's context coloring

walterl21:11:45

IIRC this (or maybe some other, similar plugin) is based on Crockford's work, yes.

sogaiu23:11:51

ah, that makes sense.

sogaiu14:11:09

i guess it would be a bit much if one used ordinary syntax highlighting for the fonts' colors and used rainbow levels for background colors 🙂

walterl22:11:20

Yeah, I agree. Seems to me like a good approach may be to use color only for context code, and only styling (bold, italic, underline) for differentiating between language elements.

martinklepsch15:11:02

So :Eval (println 1) doesn’t work in my CLJS Repl. I’m not quite sure what to do to debug so here’s some more context and maybe people have pointers: I’m (automatically as fireplace does) connecting to a ShadowCLJS nREPL. The REPL is a CLJ REPL at first, then I use shadow.cljs.devtools.api/node-repl to turn it into a CLJS REPL. After that point :Eval (println 1) no longer prints anything.

dominicm18:11:49

How do you call node-repl, just to check?

tpope18:11:26

this matches my vague recollection of my attempt to use shadowcljs as well

tpope19:11:57

if i were to debug, i would start by trying to find out what's going over the wire. see if there are :out messages with the wrong :id for example. you could do this by hacking up fireplace, using a packet sniffer, or by recreating the same setup with an nrepl client api

dpsutton19:11:44

CIDER has a way to toggle logging of nrepl messages and i've found it invaluable in diagnosing problems. quite a nice feature

tpope19:11:22

actually ch_logfile() might be sufficient for this