[HN Gopher] Show HN: Common Lisp Vim Compiler Plug-In
___________________________________________________________________
Show HN: Common Lisp Vim Compiler Plug-In
As linked in the readme at the link, I am an ardent vim user and
lisp enthusiast. I got tired of hard to read error messages in SBCL
with my vim set-up, so I spent a few days cobbling together this
`:make` plugin for sbcl Roswell. More about my rationale around why
I did it is in the readme. Let me know what you think!
Author : djha-skin
Score : 31 points
Date : 2023-12-30 23:38 UTC (23 hours ago)
(HTM) web link (git.sr.ht)
(TXT) w3m dump (git.sr.ht)
| ivanjermakov wrote:
| How this compares to using cl-lsp[1] with Neovim?
|
| [1]: https://github.com/cxxxr/cl-lsp
| fiddlerwoaroof wrote:
| LSP is the wrong interaction paradigm for CL: you might as well
| use some other language if you're going to limit yourself to
| what LSP can do.
| BaculumMeumEst wrote:
| I would think that logic should apply to Clojure as well yet
| LSP is becoming the de-facto standard for it
| fiddlerwoaroof wrote:
| I dunno, I only use cider with Clojure. I don't even like
| LSP for the languages it's supposedly good at.
| pjmlp wrote:
| It would say it is more like Cursive is, at least for those
| that see value paying for their tools.
| djha-skin wrote:
| cl-lsp isn't very mature yet. I still use it, but it doesn't
| provide much by way of completion or checking.
| aidenn0 wrote:
| Why not just run the compilation though emacs/slime, and let
| emacs figure out the line numbers for you?
|
| See e.g. https://github.com/jasom/geany-lisp for a plug-in for a
| different editor that does this.
___________________________________________________________________
(page generated 2023-12-31 23:02 UTC)