config_tree

The file layouit

.
├── init.lua                -- The entrypoint for the configuration
├── lazy-lock.json          -- Version Control
└── lua
    ├── autocommands.lua    -- Autocommands
    ├── keymaps.lua         -- Keymaps for neovim
    ├── Lazy.lua            -- Auto installation and configuration of
    ├── options.lua         -- Neovim settings
    ├── settings            -- LSP settings
    │   ├── lua_ls.lua
    │   └── pyright.lua
    ├── user                -- Auto loaded configurations
    │   ├── alpha.lua
    │   ├── autopairs.lua
    │   ├── bufferline.lua
    │   ├── cmp.lua
    │   ├── colorscheme.lua
    │   ├── comment.lua
    │   ├── dap.lua
    │   ├── dapui.lua
    │   ├── gitsigns.lua
    │   ├── illuminate.lua
    │   ├── indentline.lua
    │   ├── lsp.lua
    │   ├── lualine.lua
    │   ├── mason.lua
    │   ├── null-ls.lua
    │   ├── nvim-dev-icons.lua
    │   ├── nvim-tree.lua
    │   ├── project.lua
    │   ├── telescope.lua
    │   ├── toggleterm.lua
    │   ├── treesitter.lua
    │   └── which-key.lua
    └── utils               -- Anything that can be accesed by anything (LSP names, DAP)
        └── init.lua

Why have a separate folder for configs?

• We use a separate folder for plugins configurations to avoid loading loop.
  I.E: Having a file lua/dap.lua and tryin to configure dap will call that file instead of the actual plugin.

Why aren't LSP settings under lua/user/lsp/settings any more like they are in neovim-from-scratch?

• The simple reason is that Lazy tries to source them as separate configs like it does with mason.lua only it errors out. While it is possible to stop Lazy from sourcing the file, LSP might try to pick it up as a settings instead.

Why have autocommands, options, and keymaps been moved out of lua/user?

A) Lazy needs a map leader, which is being set inside the keymaps.lua.
B) Lazy cannot load those files because they don't return the proper data like plugin configs do.
C) We do not require lazy loading in these, and it's nice to have decent defaults.

What is the utils folder for?

A) As of right now it is not used for much other than being sourced by mason-lspconfig and nvim-lspconfig to configure and install necesarry language servers.
B) Mainly to be sourced when a little function needed to filter specific text input or such by a lot of different plugins.