nvim-metals VS bspwm

By multiple subprojects are they independent builds? Or just one big build with nested build files? I actually have a discussion related to this in here. Please to jump in there if that's the same issue you're having and comment on your situation. It'll be helpful to determine how to address it.

Use nvim-metals

elixir.nvim is a langauge plugin for Elixir. It is similar to nvim-metals in that is manages ElixirLS (Elixir's language server) and provides a complete experience over nvim-lspconfig.

Install https://github.com/scalameta/nvim-metals

But I haven't yet set up anything properly other than Debugpy. nvim-dap is very barebones, so I feel that the best way is to have an extra configuration plugin on top. Debugpy.nvim is a very specific frontend plugin, but there are also more general plugins like nvim-metals and vim-ultest which also offer integration with nvim-dap.

Yeah it's pretty good already and getting newer features everyday. I didn't want to hook up the vim I use everyday to a heavy editor so installed neovim alongside vim on my system and use this https://github.com/scalameta/nvim-metals (which I believe is the metals official way) and it's super straight forward to use.

Every software project is WIP to some extent, but that doesn't stop Neovim itself from having really high standards in documentation. A lot of Neovim plugins also have really high standards, such as nvim-metals.

nvim-metals (really thorough manual)

Bspwm is a window manager. Configuration happens in $XDG_CONFIG_HOME/bspwm/bspwmrc, as per stated here: https://github.com/baskerville/bspwm

Use BSPWM. It supports right clicks by default and its modular. You might want to look for status bars that work with it, slstatus does not work. Good luck, supremacist!

I had not heard of bspwm but I am a fan of telling WMs. Looking at the documentation now, I really like the pragmatic approach lol https://github.com/baskerville/bspwm

If you use the bspwm off of github instead of the old 0.9.10, you can use bspc node @parent -y next to cycle the split type of the parent of the focused. I added it ~1.5years ago, after baskerville added node -y horizontal and node -y vertical to set the split type of a node to vertical/horizontal ~2 years ago.

Also bspwm's JSON generation and parsing is not great. If you have a window with quotes in its class name, bspwm, when dumping it, will not escape them generating invalid JSON (e.g. {"className":"the "cool" window",) that jq will not be able to read, and even worse, bspwm itself will not be able to read. (Yes, if a window's class name contains a " character, bspwm will fail to reload after you run wm -r #1362).

Just follow this guide

Pencere yöneticisi: bspwm