Help with moving setup() files into lazy config sections

[TC72]

My previous set-up was packer, to organise things I had separate _config.lua files to handle the setup() options of plugins I installed.
What I ended up with was a long list of config files I called after the plugins were loaded.

This is a very simple example of a tabline_config.lua files I use but others are much larger:

require'tabline'.setup {
    enable = false,
    options = {
        show_filename_only = true,
        show_bufnr = true
    }
}

I've moved over to lazy and one of the things I wanted to do was call these files as part of the lazy config.

    {
        "kdheepak/tabline.nvim",
        config = require('tabline_config')
    },

I can't get it to work as the order of plugins being loaded and configured is important.
A prime example is Plenary and Telescope. I must set up Plenary first as my Telescope set-up relies on it. But i just can't get it to work, always get error messages about Plenary being missing.

I want to move over to having all this code handled by files in the plugins directory but that would be a similar issue, how do I decide the order if they're just separate files in the directory that get loaded automatically?

[TC72]

I'll post this in case it helps someone else but using priority and calling my config correctly, inside a function() ... end, has fixed my issue.

    {
        'nvim-lua/plenary.nvim',
        lazy = false,
        priority = 300,
        config = function()
            require('plenary_config')
        end
    },

    {
        'nvim-telescope/telescope.nvim',
        tag = '0.1.0',
        priority = 200,
        config = function()
            require('telescope_config.init')
            require('telescope_config.setup')
            require('telescope_config.mappings')
        end
    },

[TC72]

I do seem to have to tell lazy that plenary is a dependency of telescope.
This config works every time:

    {
        'nvim-lua/plenary.nvim',
        config = function()
            require('plenary_config')
        end
    },

    {
        'nvim-telescope/telescope.nvim',
        tag = '0.1.0',
        dependencies = {'nvim-lua/plenary.nvim'},
        config = function()
            require('telescope_config.init')
            require('telescope_config.setup')
            require('telescope_config.mappings')
        end
    },

If I remove the dependencies then I will sometimes get an error because the telescope config relies on something which gets configured by the plenary config. It seems to be completely random.

This isn't a complaint, I have no problem using dependency.

[folke]

What exactly is in your plenary_config file?

[TC72]

I copied TJ Devries set-up for plenary and telescope. This is what plenary config does.
I know it's not a normal setup(), but it makes these functions available for other configs to use them, including my telescope config.

local ok, plenary_reload = pcall(require, "plenary.reload")
if not ok then
  reloader = require
else
  reloader = plenary_reload.reload_module
end

P = function(v)
  print(vim.inspect(v))
  return v
end

RELOAD = function(...)
  return reloader(...)
end

R = function(name)
  RELOAD(name)
  return require(name)
end

function _G.dump(...)
    local objects = vim.tbl_map(vim.inspect, {...})
    print(unpack(objects))
end

[TC72]

In my packer set-up this was just called globals.lua and I'd require it before any packer code. Because Lazy needs to be configured 1st to set-up the rtp I had to move this somewhere else. Linking it to plenary loading seemed like a good idea.

[folke]

hmm, it should really still all work without dependencies. In my own config (and LAzyVim) and in most people's configs, dependencies are only infrequently used when needed for vimscript plugins.

What is the error you get?

[TC72]

[TC72]

This is the top of the telescope_config/init.lua:

local should_reload = true
local reloader = function()
  if should_reload then
    RELOAD('plenary')
    RELOAD('popup')
    RELOAD('telescope')
  end
end

reloader()

[TC72]

I know the main issue here is me blindly copying TJ's config without really understanding what I need, not an issue with Lazy 👍

[folke]

ok, I got it now. That's to be exepcted. It's becuase of the global.

You can use dependencies here for sure, or you could add a require("plenary") in your telescope config(). That would have autoloaded plenary and it's config.

So dependncies are fine here :)

[TC72]

Perfect, thanks again for your help.
Have a great weekend.

[folke]

you too!