Automatic update plugins *
* actually semiautomatic;)
Somehow quietly on VIM's blog, apparently everyone is sleeping - or maybe the huge .vimrc ended up on the Internet? ;) It is not known, but it is clear that you need to break this silence.
I will break it today with one good plugin, the references of which I have not found here. This is GetLatestVimScripts (http://vim.sourceforge.net/scripts/script.php?script_id=642).
')
To start a small outline of the presentation
// FIXME : Habrahabr developers, guys. Well for crap with links going on? Is this XSS protection such that the word script is distorted everywhere? Previously, this was not.
For all - s & # 99; ript in the links you need to replace the script.
In principle, the name is already clear;) Deployed - in order for you to update some plugins - either simply by downloading new versions to a specific folder, or by additionally automatically installing.
Why is this plugin needed by someone? The answer is simple - because it is difficult to keep track of everything manually, you need to remember what is installed and what version. And this is despite the fact that many useful scripts are updated less frequently.
Most of all, wget is needed - without it, a little happiness will not work. It is also very desirable to have an updated version of Vimball (which is also not simple and wants to vim from version 7.0), but we will assume that it is already updated, because vim 7.2. If someone is not updated - write, let's figure it out.
Since we have wget, we’ll use it
After that, the directory GetLatest will appear in the .vim directory (vimfiles for win), in which GetLatestVimScripts.dist will be located. This file is supplied by default as an example. To use it, you must rename GetLatestVimScripts.dat
His content is as follows.
Where
ScriptID - script id at http://vim.sourceforge.net/ (for example, for GetLatestVimScripts is 642, which can be seen only by pointing to a link).
SourceID - for a start it is better to set it equal to 1. In general, this is src_id for sourceforge, which changes for each new version of the script.
Filename is the name of the script, which may contain spaces (confusion may arise here, so I will explain - in fact, the name can be anything and does not have to match the name of the file being downloaded or the name of the script).
It is worth mentioning such a parameter as : AutoInstall:, which is located between the SourceID and the Filename (for example, my GetLatestVimScripts.dat)
This parameter, as many have already guessed, is needed in order for the plugin to be automatically installed. GetLatestVimScripts is smart enough and can work with almost all types of files that come with plugins for vim.
But enough explanations - I have already said quite a lot, the rest can be found out by asking a question, or by reading the description inside the plugin itself.
Using is extremely simple - you just need to run the command: GLVS. After that, the process will go - and notify at the end what happened. If there are plugins that are simply downloaded, they will be placed in ~ / .vim / GetLatest /.
At the moment, the ability to specify the folder into which files will be unpacked (most archives by default unpacked to ~ / .vim, and * .vim files - to ~ / .vim / plugin) is most lacking - which would be convenient for some scripts - for example, color schemes. Another disadvantage is that the plugin does not work with * .tgz - because of what my XPTemplate does not want to be updated. This is of course the most noticeable to me - and the reason to contact the author.
That's enough;) Have a happy work!
Somehow quietly on VIM's blog, apparently everyone is sleeping - or maybe the huge .vimrc ended up on the Internet? ;) It is not known, but it is clear that you need to break this silence.
I will break it today with one good plugin, the references of which I have not found here. This is GetLatestVimScripts (http://vim.sourceforge.net/scripts/script.php?script_id=642).
')
To start a small outline of the presentation
- What is this plugin for?
- How to install and what is needed
- How to use
- What is missing
// FIXME : Habrahabr developers, guys. Well for crap with links going on? Is this XSS protection such that the word script is distorted everywhere? Previously, this was not.
For all - s & # 99; ript in the links you need to replace the script.
1. What is this plugin for?
In principle, the name is already clear;) Deployed - in order for you to update some plugins - either simply by downloading new versions to a specific folder, or by additionally automatically installing.
Why is this plugin needed by someone? The answer is simple - because it is difficult to keep track of everything manually, you need to remember what is installed and what version. And this is despite the fact that many useful scripts are updated less frequently.
2. How to install and what is needed
Most of all, wget is needed - without it, a little happiness will not work. It is also very desirable to have an updated version of Vimball (which is also not simple and wants to vim from version 7.0), but we will assume that it is already updated, because vim 7.2. If someone is not updated - write, let's figure it out.
Since we have wget, we’ll use it
wget http://vim.sourceforge.net/scripts/download_script.php?src_id=8136 -O getscript.vba.gz
vim getscript.vba.gz
: so%
: q After that, the directory GetLatest will appear in the .vim directory (vimfiles for win), in which GetLatestVimScripts.dist will be located. This file is supplied by default as an example. To use it, you must rename GetLatestVimScripts.dat
mv ~ / .vim / GetLatest / GetLatestVimScripts.dist ~ / .vim / GetLatest / GetLatestVimScripts.dat
His content is as follows.
ScriptID SourceID Filename -------------------------- 294 1 Align.vim 302 2 AnsiEsc.vim 122 3 astronaut.vim 104 4 blockhl.vim 120 5 decho.vim 40 6 DrawIt.tar.gz 451 7 EasyAccents.vim 195 8 engspchk.vim 642 9 GetLatestVimScripts.vim 489 10 Manpageview.vim 551 11 Mines.vim 514 12 mrswin.vim 670 13 visincr.vim 628 14 SeeTab.vim 508 15 ZoomWin.vim 877 16 gvcolor.vim
Where
ScriptID - script id at http://vim.sourceforge.net/ (for example, for GetLatestVimScripts is 642, which can be seen only by pointing to a link).
SourceID - for a start it is better to set it equal to 1. In general, this is src_id for sourceforge, which changes for each new version of the script.
Filename is the name of the script, which may contain spaces (confusion may arise here, so I will explain - in fact, the name can be anything and does not have to match the name of the file being downloaded or the name of the script).
It is worth mentioning such a parameter as : AutoInstall:, which is located between the SourceID and the Filename (for example, my GetLatestVimScripts.dat)
ScriptID SourceID Filename
--------------------------
2611 11899: AutoInstall: XPTemplate
1658 11834: AutoInstall: NERDTree
159 3640: AutoInstall: MiniBufExplorer
69 6273: AutoInstall: Project
273 7701: AutoInstall: TagList
90 11049: AutoInstall: VCSCommand
489 9573: AutoInstall: ManPageView
39 8196: AutoInstall: MatchIt
642 8136: AutoInstall: getscript.vim This parameter, as many have already guessed, is needed in order for the plugin to be automatically installed. GetLatestVimScripts is smart enough and can work with almost all types of files that come with plugins for vim.
But enough explanations - I have already said quite a lot, the rest can be found out by asking a question, or by reading the description inside the plugin itself.
3. How to use
Using is extremely simple - you just need to run the command: GLVS. After that, the process will go - and notify at the end what happened. If there are plugins that are simply downloaded, they will be placed in ~ / .vim / GetLatest /.
4. What is missing
At the moment, the ability to specify the folder into which files will be unpacked (most archives by default unpacked to ~ / .vim, and * .vim files - to ~ / .vim / plugin) is most lacking - which would be convenient for some scripts - for example, color schemes. Another disadvantage is that the plugin does not work with * .tgz - because of what my XPTemplate does not want to be updated. This is of course the most noticeable to me - and the reason to contact the author.
That's enough;) Have a happy work!
Source: https://habr.com/ru/post/78828/
All Articles