Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of after directory, antipattern. #60

Open
navneetankur opened this issue Jun 8, 2023 · 0 comments · May be fixed by #61
Open

Use of after directory, antipattern. #60

navneetankur opened this issue Jun 8, 2023 · 0 comments · May be fixed by #61

Comments

@navneetankur
Copy link

This plugin uses after directory to run a script.
But if you don't use any plugin manager and rely on pack/*/opt directory and packadd command to load plugin. The script in after directory is not sourced. Causing the plugin to not function.

After directory was supposed to be used by system admins and not plugins. I know now plugin managers source the scripts in after directory, but is it really needed here.

If someone is using plugin manager they should ensure that this plugin's autocmd is run correctly. Instead of authors using the after dir.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant