kylo252

> Now, there will be probably some problems still with projects pre Ivy (< v9, released in 2020) due to this https://github.com/neovim/nvim-lspconfig/issues/1155#issuecomment-900850735 here are some problems we need to address...

I've added this page a while ago: https://www.lunarvim.org/troubleshooting/ Feel free to send PR to update the page with any relevant problems.

> @kylo252 The installer uses `cargo` to install ripgrep and fd-find The thing is that you can install these _through your package manager or something_ and never have to deal...

> Maybe I did, but the isntaller never asked me so I don't even now where I should've been looking. Which system did you say you were using? I know...

> There are also cases, like on macOS, where the package manager is unreliable and often comes with out of date software and in the case of Homebrew, it often...

> I wonder if LunarVim is even capable of finding that weird `fdfind` command. I'm always hesitant to how much additional processing I can do in the installer because it's...

> But that's something the user has to do. It's obviously be much more convenient for the installation script to do that job. I don't think it's that easy to...

> So we'd need to publish LunarVim on all kinds of package managers? Only the most popular ones from each platform: - Linux: PKGBUILD and maybe Nix - OSX: Homebrew...

> You need to run `DBInstall`. Documentation is outdated. Currently they're using `dap-buddy.nvim` which is sparse on documentation as well. `dap-buddy.nvim` should be superseded by `mason.nvim`

> Or is there a reason why we don't use `vim.fn.system()` (which should do this automatically) instead of `uv_spawn` (`vim.loop.spawn`))? the reason is explained in the original change, see https://github.com/neovim/neovim/pull/16430...