vim-sexp
lispyville
| vim-sexp | lispyville | |
|---|---|---|
| 5 | 4 | |
| 601 | 312 | |
| - | - | |
| 0.0 | 0.0 | |
| about 3 years ago | almost 2 years ago | |
| Vim Script | Emacs Lisp | |
| MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vim-sexp
-
Can I remap `yi{` to something like `yicb`?
Also, there is a popular name "f" as "form" for such mappings (like `yif`) which is used in Lisps (in Emacs, in vim-sexp).
-
How to create custom operator-pending mappings for evil
One type of operation I'm finding hard time to replicate is the custom operator-pending mappings. In lisp like files, I use operators from vim-sexp a lot.
-
Lisp programming configuration for neovim
You may also want to try vim-sexp if you decided to use parinfer and disable nvim-autopairs.
-
Fighting with SLIME's auto paren balancing
with vim-sexp if you have
-
Do you use Paredit?
but i use vim so i use this: https://github.com/guns/vim-sexp
lispyville
-
paredit.vim – Paredit Mode: Structured Editing of Lisp S-Expressions
Noctuid, of `general.el` fame, has a related package which integrates lispy's approach with `evil.el` better.
https://github.com/noctuid/lispyville
-
Does anybody else find Evil very painful for working in lisp?
Yes, this or lispyville
-
Smartparens bindings for evil users
Try https://github.com/noctuid/lispyville.
-
Do you use Paredit?
I've had some issues with paredit, like ending up with a stray orphaned paren that was impossible to delete (this has happened more times than I care to admit). So a while ago I started shopping around and tried out lispyville (evil-mode FTW). Yes, the initial setup was a little more involved, but once I figured out the Key themes I wanted, it was golden. Never looked back. The main README here on the lispyville github repo explains the various Key themes and how to enabled them. I enabled most of them, and I think the only thing I added was a hook for lispy-stringify. The awesome thing is we have lots of choices, though, so whatever works for you is what you should use.
What are some alternatives?
nvim-ts-rainbow - Rainbow parentheses for neovim using tree-sitter. Use https://sr.ht/~p00f/nvim-ts-rainbow instead
tree-edit - 🌲 Structural editing in Emacs for any™ language!
dotfiles - Configuration for Linux, i3, Kitty, Fish, Neovim and more
yaelispy - Minor mode to integrate Lispy and Evil
nvim-parinfer - parinfer for Neovim
paredit - Official mirror of Paredit versions released on vim.org
parinfer-rust - A Rust port of parinfer.
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
conjure - Interactive evaluation for Neovim (Clojure, Fennel, Janet, Racket, Hy, MIT Scheme, Guile, Python and more!)
vim-slime - A vim plugin to give you some slime. (Emacs)
dotfiles - config info
vlime - A Common Lisp dev environment for Vim (and Neovim)