What is the easiest way to re-enable the standard matchparen plugin?

[bluz71]

I switched over from Packer to Lazy last week, mostly a smooth process.

Today however I did notice that parenthesis were not being matched. A bit of debugging via the :scriptnames command indicates that nvim/runtime/plugin/matchparen.vim is not being loaded.

The Lazy README appears to have a rtp/disabled_plugins section that implies all standard plugins are not loaded. That's fine, a good performance choice.

However, if I want to use matchparen (just that plugin) what is the easiest way of doing that?

[Chaitanyabsprip]

you can add the path of matchparen plugin to this config option, performance/rtp/paths. you can find more about the option in the docs.

[bluz71]

Do you have exact syntax for that?

I tried always these combinations and none worked:

  performance = {
    rtp = {
      paths = {
        "/usr/local/nvim-linux64/share/nvim/runtime/plugin/matchparen.vim",
        "/usr/local/nvim-linux64/share/nvim/runtime/plugin/matchparen",
        "plugin/matchparen.vim",
        "plugin/matchparen",
        "matchparen.vim",
        "matchparen",
      },
    },
  },

[bluz71]

This appears to work:

local runtime = vim.cmd.runtime

lazy.setup({
-- All the plugins I want in here
})

-- Load up the standard matchparen plugin (which is explicitly disabled by lazy.nvim).
runtime("plugin/matchparen.vim")

Problem solved.
However, if someone else has a more elegant solution, then by all means let me know.

Cheers.

[folke]

No builtin plugins are disabled by default, unless you copied the example and uncommented the line with matchparen?

[bluz71]

No I did not do that.

matchparen was not being loaded for me.

Would you consider that a bug? If so, I will form up a minimal test case and create an issue.

[folke]

It should show under that section.

Would be great if you could provide a minimal repro

[bluz71]

Yes, I will do that tomorrow.

Maybe I had some Neovim options set that interfered, possible. Sounds like the issue is more likely to be my setup.

I will be in touch either way, either a new issue with minimal setup or an update here with mea-culpa.

[folke]

You should obviously not set vim.g.loaded_matchparen=1, since that would skip loading the plugin internally

[bluz71]

I don't do that.
Something else is going on.
Noting that matchparen was working automatically when I was using packer.
To be determined soon.

[bluz71]

New issue created, #306