Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Hello community. I want to introduce my new plugin nvlime - which is a fork of old vim plugin Vlime (which in its turn alternative for slime extension for Emacs - Common Lisp development environment).
Yeah, mapping a function instead of a mapping is even better. I just don't like if a predefined mapping is hard to remember or (even worse) conflicts with one of my existing mappings. Personally I like it the way Neovim's LSP client does it: you get a Lua (or Vim script) API that you can map yourself. In my info.vim I provide the commands :InfoNext, :InfoPrev and :InfoUp, but I also have a code snippet of reasonable default bindings in my README that people can just copy-past into their configuration. If they disagree with my defaults they can then change that snippet instead of having to fight my plugin to scrub away the defaults.
Related posts
- Common Lisp development environment for Neovim
- Emacs4CL: A 50 line DIY kit to set up vanilla Emacs for Common Lisp
- 15 Best Lisp Courses to Take in 2023, for Emacs Lisp, Common Lisp, Scheme and Racket, by ClassCentral -featuring System Crafters
- Does anyone use vim for lisp dev?
- So i wanna learn Common Lisp