Clojurians Log v2

Have you given any thought to incorporating parinfer?

Hi @mark340 I have sometimes considered it, mostly as a "selling point", since I am not going to use it myself. I would prefer not to write parinfer in Clojure from scratch, so I have occasionally looked at existing implementations and tried to figure out, if there is some way to wrap it. Ironically I cannot find any Clojure (or JVM based) implementations of parinfer. So I do not have any fixed plans, but I get around it once in a while and maybe some day I feel inspired and go for it, one way or the other. (Thats actually how most of my ideas get to life, including Liquid itself.) When people like you mention it, I take an extra roundtrip to see, if the time is now 🙂

@mogenslund - are you going to support LSP?

@srijayanth Hah. I can't believe I have written a text editor with focus on writing code and never heard of LSP. It sounds like some very useful feature, so it will definitly be worth investigating. I will put it on my study list. Let me know if there are any existing libraries I should use or be inspired from. Until then, there are already some homemade features for looking up functions and for goto-definition. with C-space C-space (yes, twice) you will get a typeahead of all public functions on the classpath. (It will try to shorten based on ns alias on insert.) For goto-definition type: "O" (shift+o). If it is a filename it will try to navigate to that file. If it looks like a function it will try to find the function. It is not 100% accurate (If it opens an unexpected buffer type c-w to kill the buffer again).

Cool. There seems to be very little work on LSP. @pez who does Calva for VSCode has played with it a bit for sure

Great. Calva looks very cool. I will go learn how it works.

Actually, I have looked very little at it. Calva uses nrepl. But the little I have been checking out LSP looks very good.