How do i disable the plugin automatically taking over vim.ui.select?

[TympanicLemon]

I tried using the deregister command, and nothing happend and I am using the basic config that it recommends in the readme

I know I must be missing something, but figured I would ask anyway
Specifically, this is because i want dressing and/or trouble to deal with some of the lsp stuff like code actions or go to definition, and for now at least, only want fzf-lua to deal with finding files, or finding git stuff etc

[ibhagwan]

The plugin doesn’t automatically take over ui.select, if you’re using LazyVim it registers using register_ui_select, which you can revert with :FzfLua deregister_ui_select.

[TympanicLemon]

First off, thanks for the response! Secondly, I am not using lazyvim
Here is my config:

return {
"ibhagwan/fzf-lua",
dependencies = { "nvim-tree/nvim-web-devicons" },
opts = {},
keys = {
{"", function () require("fzf-lua").files() end, desc = "Find files fzf"},
{"ff", function () require("fzf-lua").files() end, desc = "Find files fzf"},
},
}

I tried getting rid of the keys section, and that didn't change anything (which it shouldn't anyway)
And, i tried using that command, it seemingly works since i get the notification that hey its being deregistered, but fzflua STILL overrides it

I could be wrong, but maybe it has something to do with the way my lsp stuff is configured?

return {
  "neovim/nvim-lspconfig",
  dependencies = {
    { "williamboman/mason.nvim", config = true },
    "williamboman/mason-lspconfig.nvim",
    "WhoIsSethDaniel/mason-tool-installer.nvim",
    { "j-hui/fidget.nvim", opts = {} },
  },
  config = function()
    vim.diagnostic.config({
      signs = false,
      underline = true,
      virtual_text = false,
      update_in_insert = true,
    })

    vim.api.nvim_create_autocmd("LspAttach", {
      group = vim.api.nvim_create_augroup("lsp-attach", { clear = true }),
      callback = function(event)
        local map = function(keys, func, desc, mode)
          mode = mode or "n"
          vim.keymap.set(mode, keys, func, { buffer = event.buf, desc = "LSP: " .. desc })
        end

        map("<leader>la", vim.lsp.buf.code_action, "Code actions", { "n", "x" })
        map("<leader>ld", vim.diagnostic.open_float, "Show diagnostics")
        map("<leader>lr", vim.lsp.buf.rename, "Rename symbol")
      end,
    })

    local function disable_semantic_tokens(client, _)
      if client.supports_method("textDocument/semanticTokens") then
        client.server_capabilities.semanticTokensProvider = nil
      end
    end

    local capabilities = require("blink.cmp").get_lsp_capabilities()

    local servers = {
      clangd = {},
      pyright = {},
      lua_ls = {
        settings = {
          Lua = {
            completion = {
              callSnippet = "Replace",
            },
            diagnostics = {
              disable = { "missing-fields" },
              globals = { "vim" },
            },
          },
        },
      },
    }

    require("mason").setup()

    local ensure_installed = vim.tbl_keys(servers or {})
    -- List of tools
    vim.list_extend(ensure_installed, {
      "stylua",
    })

    require("mason-tool-installer").setup({ ensure_installed = ensure_installed })
    require("mason-lspconfig").setup({
      handlers = {
        function(server_name)
          local server = servers[server_name] or {}
          server.capabilities = vim.tbl_deep_extend("force", {}, server.capabilities or {}, capabilities)
          require("lspconfig")[server_name].setup(vim.tbl_extend("force", server, {
            on_init = disable_semantic_tokens,
          }))
        end,
      },
    })
  end,
}

Other than that, i have no idea what is going on.

[ibhagwan]

I could be wrong, but maybe it has something to do with the way my lsp stuff is configured?
Other than that, i have no idea what is going on.

FzfLua will never register itself automatically, maybe you’re using another plugin that does that like dressing.nvim?

Try with mini.sh you’ll see, fzf-lua never registers automatically, it’s not in the code, search somewhere in your config/plugins.

[TympanicLemon]

Oh, weird, why would dressing make fzf lua take over the ui select, weird lol (for me at least)
But that fixed it! Will try and see if the docs have any way to stop that since the whole point of having dressing is to use that for code actions and stuff like that, not fzf.

Thanks man! :D

[ibhagwan]

Oh, weird, why would dressing make fzf lua take over the ui select, weird lol (for me at least) But that fixed it! Will try and see if the docs have any way to stop that since the whole point of having dressing is to use that for code actions and stuff like that, not fzf.

Thanks man! :D

It has a default backend depends on what’s installed, for the logic behind that you’d have to ask in that repo :)