dotfiles VS refactoring.nvim

My dotfiles are on github so have a look if you want. Plugins are here https://github.com/rcarriga/dotfiles/blob/master/.config/nvim/lua/plugins.lua, with config for most in their own lua file and the colorscheme defined in `lua/colors.lua`. Not the tidiest though!

If you see a theme you like go the the authors profile and look for a dotfiles repo. You'll usually find an answer. https://github.com/rcarriga/dotfiles/blob/master/.config/nvim/lua/colors.lua

im using this setup https://github.com/rcarriga/dotfiles/tree/master/.config/xmonad and it kind of works but you have to manually update the xmonad and xmonad-contrib commits in stack.yaml since it uses old versions

Not that difficult just a bit different. The best way I've found is to create a FIFO stream and store your workspace state there. My setup highlights the current workspace and the currently selected window. Each window is given an icon and you can add icons for new window classes. Here's the source https://github.com/rcarriga/dotfiles/blob/master/.config/xmonad/src/main.hs#L200

Treesitter is a syntax parser that'll build a tree-like structure to enable anything from excellent syntax highlighting through to complex refactoring. There are so many creative ways you can use Treesitter, from jumping around text objects to commenting sections of code, it's a must-have in my books.

Is there any refactoring plugins for Neovim besides https://github.com/ThePrimeagen/refactoring.nvim?

refactoring.nvim is, that I know of, the closest we have to IDE-like refactoring features such as this, but does not have this feature. It would make C development much nicer imo. Perhaps a feature request there may gain traction.

I'm trying to make a naive implementation of command-preview for refactoring.nvim. Currently, my naive implementation is working (since the changes made to a buffer for previewing are discarded by neovim, I'm executing the plugin regularly in order to preview the changes and when the user submits the command to make the changes).

refactoring.nvim and null-ls.nvim may help

refactoring.nvim is one option. Unfortunately what powers VSCode is the proprietary PyLance and AFAIK there is no way to "Move symbol to file (method will be moved) [and have imports renamed subsequently]".

Just a heads up, I added a lot of Ruby support in ThePrimeagen's Refactoring.nvim plugin some time ago. Covers a lot of what you've created and has support for lots of other languages too

It's a pain to learn. I used the online playground and also read a lot of the queries from popular plugins. I contributed Ruby support to refactoring.nvim which helped me learn a tonne too

You might be able to take the ruby one and make an elixir one. It uses tree-sitter queries which you would need to align up with the elixir, but the syntax is kinda close. See https://github.com/ThePrimeagen/refactoring.nvim/blob/master/lua/refactoring/treesitter/langs/ruby.lua