aniseed VS splitjoin.vim

aniseed

You don't need to transpile it if you use https://github.com/Olical/aniseed

Something similar: Fennel (https://fennel-lang.org/) is a lisp that compiles into Lua, which nvim can use as plugins, so you can write nvim plugins in a lisp. Aniseed (https://github.com/Olical/aniseed) makes this really easy.

Just use vim. Yes, emacs has a lisp engine, but so does nvim[1]. Really, though, using vim properly means that it doesn't need to swallow the kitchen sink[2]. Just use vim.

1: https://github.com/Olical/aniseed

2: https://blog.djha.skin/p/emacs-users-im-okay-i-promise/

I use Aniseed to write my configs in Fennel, and I can't seem to find a way to get Aniseed bootstrapped and managed by lazy. Folke has said that fennel isn't supported in issues about hotpot and tangerine, but neither of them particularly help me solve my issue

:!git clone https://github.com/Olical/aniseed /home/USER/.local/share/nvim/site/pack/packer/start/aniseed Cloning into '/home/USER/.local/share/nvim/site/pack/packer/start/aniseed'...

Have you tried aniseed ?

Aniseed: mostly an environment, it does handle configuration. It adds a lot of clojure features (another modern Lisp) such as a module system. It does seem to be slower to startup though, but I really like how its module system works and still use it for that reason alone. There's not much boilerplate code, just add it to the header

The easiest would be to use aniseed: https://github.com/Olical/aniseed, it has a bootstrap script that downloads all the needed dependencies: https://github.com/Olical/aniseed, it also adds some syntax niceties and testing support. Here's an example of a plugin: https://github.com/katawful/kat.nvim

My splitjoin plugin handles your examples, in case you're open to non-LSP, non-treesitter solutions: https://github.com/andrewradev/splitjoin.vim

To avoid the practical issues with master/main, a simple solution is to mirror branches in a github action. I had to fork the action itself to fix an issue, but yeah, it works fine.

Yes, sorry, should have done that the first time I encountered the bug. I rediscovered the bug and I opened a new issue.

I quite like https://github.com/AndrewRadev/splitjoin.vim . There are defaults for some filetypes and you can add "recipes" for whatever you want.

splitjoin to alternate between abbreviated and expansive syntaxes for hashes, arrays, method calls...

To clarify a bit, "a regex approach" doesn't mean s// :). For example, I've got a few mini-parsers for specific cases like rust structs or ruby methods and hashes that handle nesting and more complex structures. Vim's built-in search functions also allow checking the syntax tree, which is how vim-ruby implements a few basic text objects, too. I feel like there's a common misconception that all of Vim is just dumb regex-matching, while regexes are just one of the tools available.

https://github.com/AndrewRadev/splitjoin.vim I noticed I often format calling a function with a lot of parameters from

For the described use case https://github.com/AndrewRadev/splitjoin.vim

I personally use this plugin: https://github.com/AndrewRadev/splitjoin.vim I usually forget I have it installed, but when I remember, it always does what in want in all the languages I use