File structure with lazy

This page summarizes the projects mentioned and recommended in the original post on /r/neovim

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • LazyVim

    Neovim config for the lazy

  • 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?

  • nvim

    personal neovim config (by ThunderSloth)

  • 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?

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts