plugin-manager
Here are 112 public repositories matching this topic...
Description
The "Requirements" wiki page has a TODO placeholder under the FreeBSD heading. The correct command to install antigen under FreeBSD is:
pkg install zsh-antigenSteps to reproduce
Visit Requirements on the z
-
Updated
Mar 3, 2020 - Vim script
I feel that the README.md is too long, that it lacks some structure that would make a large amount of information better presented.
The problem is that:
a. there are many features (i.e. large feature-set),
b. the features are often swiss-army-knives and need some elaboration, if not then users might not discover the feature-set of Zplugin.
The changes doesn't have to be a complete rephrase
Right now absolute paths in imports are still passed to git, which relativizes them. That's a security vulnerability -- the git defaults might change, or we might switch implementations without remembering this detail. We should stop doing it, and also create a test for it.
I used to use vim-plug whose documentation included an if statement you could use to drop a vimrc/init.vim on a new system and the first time you started vim, it'd install all your plugins for you. Useful if you are constantly blowing away the contents of a machine and want to easily deploy a functional environment to it.
Unfortunately minpac doesn't have such a simple single-file you can downl
When the user starts my program for the first time, the configuration folder will be created. When the user moves my program to other locations, my program cannot start
-
Updated
Feb 23, 2020 - Vim script
Hello
Almost all plugins that I know of have a README.md file at their root.
So what about a plug-doc command, that would have the all the installed plugins as auto-completion and would automatically opens the associated README.md ?
Example:
:plug-doc<space>
I select ul/kak-lsp for instance, then press Enter, Kakoune opens kak-lsp's README.md
Bonus:
Whe
-
Updated
Dec 17, 2019 - C#
-
Updated
Feb 28, 2020 - Java
-
Updated
Mar 4, 2020 - TypeScript
-
Updated
Feb 21, 2020 - Go
-
Updated
Mar 3, 2020 - Go
Moved from https://bro-tracker.atlassian.net/browse/BIT-1826
Last night I upgraded a Bro installation from a late 2.4 version to git master and I realized that I didn't have an easy way to rebuild Bro plugins other than to uninstall them and reinstall them. It would be nice if there was a single bro-pkg command I could run that would just clean and rebuild all plugins.
-
Updated
Feb 7, 2020 - Python
-
Updated
Nov 6, 2019 - Shell
-
Updated
Feb 20, 2020 - Vim script
-
Updated
Aug 29, 2019 - Ruby
-
Updated
Feb 15, 2020 - PHP
-
Updated
Feb 3, 2020 - Python
-
Updated
Nov 10, 2019 - Rust
Improve this page
Add a description, image, and links to the plugin-manager topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the plugin-manager topic, visit your repo's landing page and select "manage topics."


I looked for a while now for some resources to understand more this project but I can't find any. If anyone knows about a source in English that would be great.