Where does the nixCats lua function come from?

[rafaeljacov]

-- NOTE: various, non-plugin config
require('myLuaConf.opts_and_keys')

-- NOTE: register an extra lze handler with the spec_field 'for_cat'
-- that makes enabling an lze spec for a category slightly nicer
require("lze").register_handlers(require('nixCatsUtils.lzUtils').for_cat)

-- NOTE: Register another one from lzextras. This one makes it so that
-- you can set up lsps within lze specs,
-- and trigger lspconfig setup hooks only on the correct filetypes
require('lze').register_handlers(require('lzextras').lsp)
-- demonstrated in ./LSPs/init.lua

-- NOTE: general plugins
require("myLuaConf.plugins")

-- NOTE: obviously, more plugins, but more organized by what they do below

require("myLuaConf.LSPs")

-- NOTE: we even ask nixCats if we included our debug stuff in this setup! (we didnt)
-- But we have a good base setup here as an example anyway!
if nixCats('debug') then
  require('myLuaConf.debug')
end
-- NOTE: we included these though! Or, at least, the category is enabled.
-- these contain nvim-lint and conform setups.
if nixCats('lint') then
  require('myLuaConf.lint')
end
if nixCats('format') then
  require('myLuaConf.format')
end
-- NOTE: I didnt actually include any linters or formatters in this configuration,
-- but it is enough to serve as an example.

[BirdeeHub]

:NixCats nixCatsPath will give you the path to it in the store if you want to go look at it.

:h nixCats for docs on specifically the nixCats lua plugin.

It gets generated from the information in your nix file, namely your packageDefinitions

Its just some tables written to a lua file via nix on build. Its where you get info about your nix from within lua.

If you meant "where in the code of nixCats is the nixCats plugin defined" here is the nix side of it mostly and the lua side minus your info from nix here. It gets filled in with your info and built into a plugin.

[rafaeljacov]

thanks! is it also possible to fix lua_ls warning that it can't find the global nixCats function?

[BirdeeHub]

Do you use lazydev?

Yes, several ways, with or without lazydev

For me it finds the type, but only after it sees a require('nixCats') statement for it because of lazydev unless I tell lazydev about it

So, I have in my config

require("lze").load  {
    "lazydev.nvim",
    for_cat = "neonixdev",
    cmd = { "LazyDev" },
    ft = "lua",
    after = function(_)
      require('lazydev').setup({
        library = {
          { words = { "nixCats" }, path = (nixCats.nixCatsPath or "") .. '/lua' }, -- you dont need the path to make it be quiet but you do for full completion
        },
      })
    end,
  }

and then my lua_ls settings dont have the usual things which would make it find it, because I use lazydev for that, but I have them there commented out

      settings = {
        Lua = {
          runtime = { version = 'LuaJIT' },
          formatters = {
            ignoreComments = true,
          },
          signatureHelp = { enabled = true },
          diagnostics = {
            globals = { "nixCats", "vim", "make_test" }, -- I still have it here, not needed tho with lazydev line above, but just so that it wont flash at me on startup ever.
            disable = { },
          },
          workspace = {
            checkThirdParty = false,
            library = {
              -- '${3rd}/luv/library',
              -- I use lazydev instead of the next line.
              -- This will make it find it find it without seeing a require statement.
              -- However it will also cause it to index a LOT of files on startup
              -- unpack(vim.api.nvim_get_runtime_file('', true)),

            },
          },
          completion = {
            callSnippet = 'Replace',
          },
          telemetry = { enabled = false },
        },
      },