LazyVim VS lazy.nvim

Please take a look at this issue. The culprit is the path source of nvim-cmp.

I’m having trouble understanding the preffered file structure when using lazy. I have a setup that works currently and I used this guide but I believe that this configuration defeats the purpose of lazy-loading. I also tried moving all of the plugin configs to the /nvim/plugins folder but that didn’t work, I think because when using lazy you want lazy to handle the loading not RTP. I’ve taken a look at the lazyvim github but I’m a little bit overwhelmed. I don’t understand how their nvim/init.lua doesn’t point to anything with require. Here is my config. So I think that the mistake I’m making is loading all my plugins in a table that gets passed to lazyvim but then requiring configs from my init.lua, when all of that info should get passed directly to lazy vim via multiple lua tables?

Has presets for each default plugin module in LazyVim.

I have been looking at LazyNvim and LazyVim and I would like to do something similar to in particular LazyNvim's startup text. How do configurations like this create this startup text?

See this Lazyvim issue.

You can try to mimic how LazyVim loads alpha here https://github.com/LazyVim/LazyVim/blob/main/lua/lazyvim/plugins/ui.lua

As usual, I referred to how folke does stuff for inspiration, and I want to better understand what exactly is going with the Treesitter configuration in LazyVim.

LazyVim (This is a distro in the form of a plugin, imo beats astronvimm nvchad, lunarvim for that reason alone. Check out the plugins/extras/lang directory in there. Has setup for a few languages. You can see the list here. Just raise a request for JAVA and someone will have your back))

Anyways, although i have not used them, LazyVim and LunarVim comes highly recommended. You can try these and see what suits you .

Am I reading this correctly, in the LazyVim starter, this line reads as it's importing all the plugins from the remote GitHub project, is that correct?

First, I installed NeoSolarized.nvim via lazy.nvim, so the code would be simple like the following one.

In my case, I have switched to Lazy.nvim for all of my Neovim plugin needs ( Thanks again Folke! ), so it would be great if you were at least minimally familiar with how Lazy works as well.

If you've read old tutorials about Neovim configuration you've find the way they create keymaps is a little bit different from what people do now. And if you check other people's configuration sometimes you'll find they create their keymaps using lazy.nvim. This is causing confusion among Neovim users.

The basic plugins will be downloaded on the first run using Lazy, a package manager for Neovim that loads only the necessary plugins as you use them. Once it's done you should be looking at a full-fledged IDE.

it looks more like something is wrong with your neovim install rather than your config. based on this lazy.nvim issue you may have an updated neovim binary but your neovim runtime files are not up to date. try completely reinstalling neovim.

It is possible to manage plugins yourself, but I would recommend a plugin manager such as Lazy (https://github.com/folke/lazy.nvim). There are many more plugins that most would argue are virtually essential, but these should at least be able to get you some autocompletion and highlighting without too much messing about. Be sure to read the install instructions for each of these plugins!

whenever i add this: ``` -- bootstrap lazy.nvim local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", -- latest stable release lazypath, }) end vim.opt.rtp:prepend(lazypath)

Easily updatable. Versions are stored in manifests and can be easily updated with a single command. neovim's lazy-lock.json however is managed separately by lazy.

require("keymaps") local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", -- latest stable release lazypath, }) end vim.opt.rtp:prepend(lazypath) require("lazy").setup({ "folke/tokyonight.nvim", {"nvim-treesitter/nvim-treesitter", build = ":TSUpdate"}, { 'nvim-telescope/telescope.nvim', tag = '0.1.4', dependencies = { 'nvim-lua/plenary.nvim' } } })