-
Updated
Nov 16, 2020 - Java
plugin-manager
Here are 137 public repositories matching this topic...
-
Updated
Nov 17, 2020 - Vim script
-
Updated
Oct 6, 2020 - Python
-
Updated
Nov 9, 2020 - Vim script
-
Updated
Nov 8, 2020 - C++
-
Updated
Nov 7, 2020 - Vim script
When there is no download directory specified, the operation fails without providing a path. It would be great to have one in the log
onenashev@LAPTOP-25K65LOS:/c/Users/Oleg/Documents/jenkins/demo/demo-jenkins-config-as-code$ java -jar jenkins-plugin-manager-1.0.2.jar --list -f plugins.txt --no-download
File containing list of plugins to be downloaded: plugins.txt
Reading in plugins from
-
Updated
Oct 15, 2020 - TypeScript
-
Updated
May 2, 2020 - C#
-
Updated
Sep 9, 2019 - Go
-
Updated
Jul 9, 2019 - Go
-
Updated
Aug 19, 2020 - Vim script
-
Updated
Nov 12, 2020 - Python
-
Updated
Apr 30, 2020 - C
-
Updated
Oct 28, 2020 - TypeScript
-
Updated
Nov 7, 2020 - Shell
-
Updated
Nov 17, 2020 - Python
-
Updated
Apr 3, 2018 - Shell
-
Updated
Nov 14, 2020 - JavaScript
-
Updated
Feb 16, 2018 - PHP
-
Updated
Jan 18, 2018 - Ruby
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've seen several questions about how to do an unsupervised installation of neovim (not all specific to packer); a core question here is how to ensure from your
init.vimthat all your plugins are installed on a fresh system.Vim-plug has this suggestion, and it would be nice to provide a similar snippet for packer.nvim t