dotfiles | vim-sexp | |
---|---|---|
6 | 5 | |
3 | 601 | |
- | - | |
8.1 | 0.0 | |
2 months ago | about 3 years ago | |
Common Lisp | Vim Script | |
- | MIT License |
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.
dotfiles
-
Show HN: A simple Pastebin Clone using Deno
The colors are mostly from zenburn
https://github.com/fiddlerwoaroof/dotfiles/blob/master/emacs...
-
Writing Small CLI Programs in Common Lisp (2021)
Yeah, that’s definitely where I’ve ended up: I have a lot of lisp code, but it’s more of a toolbox for my shell (REPL) than standalone programs.
However, I’ve settled on a pattern that works pretty well for the few small tools I write: https://github.com/fiddlerwoaroof/dotfiles/blob/18cecfc93bcf...
-
Show HN: Mount Unix system into Common Lisp image
I use these keys every day for just about every sort of balanced delimiter manipulation I do in any language: https://github.com/fiddlerwoaroof/dotfiles/blob/eff889f0b749...
A little below I bind this key map to the “,” prefix and I’ve found my layout of paredit commands pretty ergonomic to use long-term.
-
Paredit 25 Released
What made a difference for me was figuring out the right keybindings. The default keybindings in emacs weren’t very ergonomic and so I came up with a more convenient set of keybindings (for evil-mode, since I prefer vim-style editing). They follow a nice pattern on the keyboard and made a huge difference.
I eventually adapted them so I could have relatively consistent keybindings across vim/emacs/VSCode/IntelliJ and the results are here:
https://github.com/fiddlerwoaroof/dotfiles/blob/b13240a42fa4...
If you understand the elisp keybinding notation, it’s possible to use the C-, ones in VSCode.
-
Coming Home to Vim
Yeah, I don’t have home-manager generate configurations for vim. I have home-manager generate a symlink to my version-controlled vimrc. This way I get the quick setup benefits of home-manager without the slow reload times.
Incidentally, I just polished my script for working around that issue: https://github.com/fiddlerwoaroof/dotfiles/blob/master/scrip...
-
Do you use Paredit?
https://github.com/fiddlerwoaroof/dotfiles/blob/master/emacs.d/lisp/configurations/evil-conf.el#L67-L143
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
What are some alternatives?
lone - The standalone Linux Lisp
lispyville - lispy + evil = lispyville
smart-god-mode - No tests yet for merging into main branch!
nvim-ts-rainbow - Rainbow parentheses for neovim using tree-sitter. Use https://sr.ht/~p00f/nvim-ts-rainbow instead
vscode-emacs-mcx - Awesome Emacs Keymap - VSCode emacs keybinding with multi cursor support
dotfiles - Configuration for Linux, i3, Kitty, Fish, Neovim and more
symex.el - An intuitive way to edit Lisp symbolic expressions ("symexes") structurally in Emacs
nvim-parinfer - parinfer for Neovim
shcl - SHell in Common Lisp [Moved to: https://github.com/SquircleSpace/shcl]
parinfer-rust - A Rust port of parinfer.
vim-sexp-mappings-for-regular-people - vim-sexp mappings for regular people
conjure - Interactive evaluation for Neovim (Clojure, Fennel, Janet, Racket, Hy, MIT Scheme, Guile, Python and more!)