Skip to content

Using opts = {} when creating plugins with out a setup.lua.example #11

@JustBarnt

Description

@JustBarnt

Instead of inserting a commented-out line for the plugin when the plugin doesn't have a setup.lua.example I think we should instead just follow lazy.nvim documentation to use opts = {} that way when installing, if we just want the default configuration for plugins; which I myself tend to go with the default on quite a bit, at least during the first bit of using a plugin.

We could also add a configuration open_config that defaults to true which would still open the file in that case; if you know you want to edit the configuration right away.

I'm currently working on a PR for this if it is something you would be interested in.

  • Add configuration for whether a configuration should open after creation or not

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions