Why is there a default configuration under folder: nvim-data\lazy\LazyVim\lua\lazyvim\config

[appicon007]

Hey,

wondering why there are default configs/keymaps under the path: nvim-data\lazy\LazyVim\lua\lazyvim\config. I wanted just a clean/sleek plugin manager without pre-configurationand -keymaps. I know there is the starter configuration LazyVim but didn't expected it for the plugin-manager lazy.vim.

Did I oversee something for installation?

Used this:

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("plugins")

[dpetka2001]

You probably did something wrong on your end. lazy.nvim doesn't install LazyVim by default.

You can only install LazyVim if you do git clone https://github.com/LazyVim/starter ~/.config/nvim.

The other thing I can think of is you want to transition from LazyVim to something else and you didn't delete the directories

~/.local/share/nvim
~/.local/state/nvim
~/.cache/nvim

that were remnants of some previous installation you did.

[appicon007]

Yes, I deleted/renamed any previous config. But still the same bahaviour. Figured out then every time I install a colorscheme-plugin, the lazyvim folder with all the boilerplate got installed. Tried several colorschemes catpuccino, tokionight, nightfly. Every time the same. So it seems there is something going on under the hud by lazy.vim

Btw. it's on windows, where the folder structure is:
%AppData%\local\nvim ->init.lua and configuration
%AppData%\local\nvim-data -> plugin downloads, etc.

[dpetka2001]

First time I've heard of this and never experienced this before myself across different computers. I do have both a LazyVim installation and a pure lazy.nvim installation and in the latter there's no folder about Lazyvim in ~/.local/share/nvim.

Can you try the following:

1. mkdir ~/.config/test && cd ~/.config/test
2. Create a file init.lua with following contents

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)

-- Example using a list of specs with the default options
vim.g.mapleader = " " -- Make sure to set `mapleader` before lazy so your mappings are correct

require("lazy").setup({
	"folke/which-key.nvim",
	{
		"folke/tokyonight.nvim",
		config = function()
			vim.cmd([[colorscheme tokyonight]])
		end,
	},
})

3. NVIM_APPNAME=test nvim and wait for installation to complete
4. Restart nvim with command from step 3 and quit
5. Go to directory ~/.local/share/test/lazy and check what folders exist. There should be no LazyVim directory. I just tested it and it worked like this in my case.

[appicon007]

Interesting... this works as expected. Now I don't understand what I'm doing wrong... The difference is a separation of the config in several files.
This is my config:

AppData\Local\nvim/init.lua

require("config")

AppData\Local\nvim\lua\config\init.lua

vim.g.mapleader = ' '
vim.g.maplocalleader = ' '

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("plugins")
require("config.options")
require("config.keymaps")

AppData\Local\nvim\lua\plugins\colorscheme.lua

return {
{ "shaunsingh/nord.nvim" },

 {
   "LazyVim/LazyVim",
   opts = {
     colorscheme = "nord",
   },
 },
}
also tried e. g.
,
--	{
 --  	"catppuccin/nvim",
--   	name = "catppuccin",
 --  	lazy = true,
--   	priority = 1000,
--   	config = function()
--   	  require("catppuccin").setup({})
--   	  vim.cmd.colorscheme "catppuccin-mocha"
 --  	end,
--   	},

[dpetka2001]

Are you sure you're not using LazyVim? Because in your colorscheme.lua it looks like you're using LazyVim.

{
   "LazyVim/LazyVim",
   opts = {
     colorscheme = "nord",
   },
 },

This code specifically. So, lazy.nvim sees this in your configuration and recognizes the spec as LazyVim. Of course it won't work like LazyVim if you didn't clone the starter repository, but this is why the folder Lazyvim gets created by lazy.nvim. If you don't use LazyVim, you shouldn't even have the above code snippet in your configuration.

[appicon007]

Ah, many thanks!
This it is... copied it from somewhere and didn't know exactly what it does and thought it sets the colorscheme.