utility/telescope: custom extensions API

[NotAShelf]

Implements a basic telescope.extensions option to take a list of additional extensions with the following schema:

[
  {
  	name = "name of the extension";
  	packages = [ <package & possible dependencies>];
    setup = {
      <extensionName> = { ... }; 
    };
  }
]

Name is used to construct the load_extension line, packages are added to vim.startPlugins verbatim and all setup attrs are merged into one to be passed to telescope's own setup table.

Fixes #542.

[github-actions]

🚀 Live preview deployed from 0435104

View it here:

Debug Information

Triggered by: NotAShelf

HEAD at: telescope-ext

Reruns: 955

[ItsLiyua]

I'd be interested in this! I wanna use some telescope plugins but it's quite difficult to add them as of right now.

[horriblename]

adding your extensions to startPlugins should work fine currently

[NotAShelf]

@horriblename could you remind me what the blocker was for this? I don't think API needs further work, but if there's a blocker we can probably look at resolving it for 0.8.

[horriblename]

it was the fact that nixpkgs telescope extensions add a duplicate telescope package, and messing up lazy loading

I think our little hack (unrelated to this PR) is still working, so we can merge this in first and worry about a proper fix later

[github-actions]

✅ Preview has been deleted successfully!