Skip to content

Why use after/plugin dir for sources ? #76

@leath-dub

Description

@leath-dub

I didn't want raise this issue in nvim-cmp as it is actually not related to that plugin, more how the sources by @hrsh7th use the after/plugin dir. The problem is that this directory is not something you should use if you expect to allow a plugin be hot loaded, i.e. added to the runtimepath dynamically: for example via packadd.

See this issue vim/vim#1994. after/plugin is not loaded by the builtin package manager and as suggested by a contributor in that issue, this is a directory primarily for users not plugins.

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