diff options
Diffstat (limited to 'uvim/runtime/doc/pi_getscript.txt')
| -rw-r--r-- | uvim/runtime/doc/pi_getscript.txt | 350 |
1 files changed, 175 insertions, 175 deletions
diff --git a/uvim/runtime/doc/pi_getscript.txt b/uvim/runtime/doc/pi_getscript.txt index 756d9e83dc..2ca81bf923 100644 --- a/uvim/runtime/doc/pi_getscript.txt +++ b/uvim/runtime/doc/pi_getscript.txt @@ -1,15 +1,15 @@ -*pi_getscript.txt* For Vim version 9.2. Last change: 2026 Feb 14 +*pi_getscript.txt* For MNV version 9.2. Last change: 2026 Feb 14 > GETSCRIPT REFERENCE MANUAL by Charles E. Campbell < Original Author: Charles E. Campbell <NcampObell@SdrPchip.AorgM-NOSPAM> (remove NOSPAM from the email address) - *GetLatestVimScripts-copyright* + *GetLatestMNVScripts-copyright* Copyright: (c) 2004-2012 by Charles E. Campbell *glvs-copyright* - The VIM LICENSE (see |copyright|) applies to the files in this - package, including getscriptPlugin.vim, getscript.vim, - GetLatestVimScripts.dist, and pi_getscript.txt, except use "getscript" - instead of "Vim". Like anything else that's free, getscript and its + The MNV LICENSE (see |copyright|) applies to the files in this + package, including getscriptPlugin.mnv, getscript.mnv, + GetLatestMNVScripts.dist, and pi_getscript.txt, except use "getscript" + instead of "MNV". Like anything else that's free, getscript and its associated files are provided *as is* and comes with no warranty of any kind, either expressed or implied. No guarantees of merchantability. No guarantees of suitability for any purpose. By @@ -19,202 +19,202 @@ Copyright: (c) 2004-2012 by Charles E. Campbell *glvs-copyright* Getscript is a plugin that simplifies retrieval of the latest versions of the scripts that you yourself use! Typing |:GLVS| will invoke getscript; it will -then use the <GetLatestVimScripts.dat> (see |GetLatestVimScripts_dat|) file to -get the latest versions of scripts listed therein from https://www.vim.org/. +then use the <GetLatestMNVScripts.dat> (see |GetLatestMNVScripts_dat|) file to +get the latest versions of scripts listed therein from https://www.mnv.org/. ============================================================================== 1. Contents *glvs-contents* *glvs* *getscript* - *GetLatestVimScripts* + *GetLatestMNVScripts* 1. Contents........................................: |glvs-contents| - 2. GetLatestVimScripts -- Getting Started..........: |glvs-install| - 3. GetLatestVimScripts Usage.......................: |glvs-usage| - 4. GetLatestVimScripts Data File...................: |glvs-data| - 5. GetLatestVimScripts Friendly Plugins............: |glvs-plugins| - 6. GetLatestVimScripts AutoInstall.................: |glvs-autoinstall| - 7. GetLatestViMScripts Options.....................: |glvs-options| - 8. GetLatestVimScripts Algorithm...................: |glvs-alg| - 9. GetLatestVimScripts History.....................: |glvs-hist| + 2. GetLatestMNVScripts -- Getting Started..........: |glvs-install| + 3. GetLatestMNVScripts Usage.......................: |glvs-usage| + 4. GetLatestMNVScripts Data File...................: |glvs-data| + 5. GetLatestMNVScripts Friendly Plugins............: |glvs-plugins| + 6. GetLatestMNVScripts AutoInstall.................: |glvs-autoinstall| + 7. GetLatestMNVScripts Options.....................: |glvs-options| + 8. GetLatestMNVScripts Algorithm...................: |glvs-alg| + 9. GetLatestMNVScripts History.....................: |glvs-hist| ============================================================================== -2. GetLatestVimScripts -- Getting Started *getscript-start* - *getlatestvimscripts-install* +2. GetLatestMNVScripts -- Getting Started *getscript-start* + *getlatestmnvscripts-install* - VERSION FROM VIM DISTRIBUTION *glvs-dist-install* + VERSION FROM MNV DISTRIBUTION *glvs-dist-install* -Vim 7.0 does not include the GetLatestVimScripts.dist file which +MNV 7.0 does not include the GetLatestMNVScripts.dist file which serves as an example and a template. So, you'll need to create -your own! See |GetLatestVimScripts_dat|. +your own! See |GetLatestMNVScripts_dat|. - VERSION FROM VIM SF NET *glvs-install* + VERSION FROM MNV SF NET *glvs-install* -NOTE: The last step, that of renaming/moving the GetLatestVimScripts.dist -file, is for those who have just downloaded GetLatestVimScripts.tar.bz2 for +NOTE: The last step, that of renaming/moving the GetLatestMNVScripts.dist +file, is for those who have just downloaded GetLatestMNVScripts.tar.bz2 for the first time. -The GetLatestVimScripts.dist file serves as an example and a template for your +The GetLatestMNVScripts.dist file serves as an example and a template for your own personal list. Feel free to remove all the scripts mentioned within it; the "important" part of it is the first two lines. -Your computer needs to have wget or curl for GetLatestVimScripts to do its +Your computer needs to have wget or curl for GetLatestMNVScripts to do its work. 1. if compressed: gunzip getscript.vmb.gz 2. Unix: - vim getscript.vmb + mnv getscript.vmb :so % :q - cd ~/.vim/GetLatest - mv GetLatestVimScripts.dist GetLatestVimScripts.dat - (edit GetLatestVimScripts.dat to install your own personal - list of desired plugins -- see |GetLatestVimScripts_dat|) + cd ~/.mnv/GetLatest + mv GetLatestMNVScripts.dist GetLatestMNVScripts.dat + (edit GetLatestMNVScripts.dat to install your own personal + list of desired plugins -- see |GetLatestMNVScripts_dat|) 3. Windows: - vim getscript.vmb + mnv getscript.vmb :so % :q - cd **path-to-vimfiles**/GetLatest - mv GetLatestVimScripts.dist GetLatestVimScripts.dat - (edit GetLatestVimScripts.dat to install your own personal - list of desired plugins -- see |GetLatestVimScripts_dat|) + cd **path-to-mnvfiles**/GetLatest + mv GetLatestMNVScripts.dist GetLatestMNVScripts.dat + (edit GetLatestMNVScripts.dat to install your own personal + list of desired plugins -- see |GetLatestMNVScripts_dat|) ============================================================================== -3. GetLatestVimScripts Usage *glvs-usage* *:GLVS* +3. GetLatestMNVScripts Usage *glvs-usage* *:GLVS* Unless it has been defined elsewhere, > :GLVS -will invoke GetLatestVimScripts(). If some other plugin has defined that +will invoke GetLatestMNVScripts(). If some other plugin has defined that command, then you may type > - :GetLatestVimScripts + :GetLatestMNVScripts < The script will attempt to update and, if permitted, will automatically -install scripts from http://vim.sourceforge.net/. To do so it will peruse a +install scripts from http://mnv.sourceforge.net/. To do so it will peruse a file, > - .vim/GetLatest/GetLatestVimScripts.dat (unix) + .mnv/GetLatest/GetLatestMNVScripts.dat (unix) < or > - ..wherever..\vimfiles\GetLatest\GetLatestVimScripts.dat (windows) -(see |glvs-data|), and examine plugins in your [.vim|vimfiles]/plugin + ..wherever..\mnvfiles\GetLatest\GetLatestMNVScripts.dat (windows) +(see |glvs-data|), and examine plugins in your [.mnv|mnvfiles]/plugin directory (see |glvs-plugins|). Scripts which have been downloaded will appear in the -~/.vim/GetLatest (unix) or ..wherever..\vimfiles\GetLatest (windows) -subdirectory. GetLatestVimScripts will attempt to automatically -install them if you have the following line in your <.vimrc>: > +~/.mnv/GetLatest (unix) or ..wherever..\mnvfiles\GetLatest (windows) +subdirectory. GetLatestMNVScripts will attempt to automatically +install them if you have the following line in your <.mnvrc>: > - let g:GetLatestVimScripts_allowautoinstall=1 + let g:GetLatestMNVScripts_allowautoinstall=1 -The <GetLatestVimScripts.dat> file will be automatically be updated to +The <GetLatestMNVScripts.dat> file will be automatically be updated to reflect the latest version of script(s) so downloaded. (also see |glvs-options|) ============================================================================== -4. GetLatestVimScripts Data File *getscript-data* *glvs-data* - *:GetLatestVimScripts_dat* -The data file <GetLatestVimScripts.dat> must have for its first two lines +4. GetLatestMNVScripts Data File *getscript-data* *glvs-data* + *:GetLatestMNVScripts_dat* +The data file <GetLatestMNVScripts.dat> must have for its first two lines the following text: > ScriptID SourceID Filename -------------------------- < Following those two lines are three columns; the first two are numeric -followed by a text column. The GetLatest/GetLatestVimScripts.dist file +followed by a text column. The GetLatest/GetLatestMNVScripts.dist file contains an example of such a data file. Anything following a #... is ignored, so you may embed comments in the file. The first number on each line gives the script's ScriptID. When you're about -to use a web browser to look at scripts on http://vim.sf.net/, just before you +to use a web browser to look at scripts on http://mnv.sf.net/, just before you click on the script's link, you'll see a line resembling - http://vim.sourceforge.net/scripts/script.php?script_id=40 + http://mnv.sourceforge.net/scripts/script.php?script_id=40 -The "40" happens to be a ScriptID that GetLatestVimScripts needs to -download the associated page, and is assigned by vim.sf.net itself +The "40" happens to be a ScriptID that GetLatestMNVScripts needs to +download the associated page, and is assigned by mnv.sf.net itself during initial uploading of the plugin. The second number on each line gives the script's SourceID. The SourceID -records the count of uploaded scripts as determined by vim.sf.net; hence it +records the count of uploaded scripts as determined by mnv.sf.net; hence it serves to indicate "when" a script was uploaded. Setting the SourceID to 1 -insures that GetLatestVimScripts will assume that the script it has is +insures that GetLatestMNVScripts will assume that the script it has is out-of-date. -The SourceID is extracted by GetLatestVimScripts from the script's page on -vim.sf.net; whenever it is greater than the one stored in the -GetLatestVimScripts.dat file, the script will be downloaded -(see |GetLatestVimScripts_dat|). +The SourceID is extracted by GetLatestMNVScripts from the script's page on +mnv.sf.net; whenever it is greater than the one stored in the +GetLatestMNVScripts.dat file, the script will be downloaded +(see |GetLatestMNVScripts_dat|). If your script's author has included a special comment line in his/her plugin, -the plugin itself will be used by GetLatestVimScripts to build your -<GetLatestVimScripts.dat> file, including any dependencies on other scripts it +the plugin itself will be used by GetLatestMNVScripts to build your +<GetLatestMNVScripts.dat> file, including any dependencies on other scripts it may have. As an example, consider: > - " GetLatestVimScripts: 884 1 :AutoInstall: AutoAlign.vim + " GetLatestMNVScripts: 884 1 :AutoInstall: AutoAlign.mnv -This comment line tells getscript.vim to check Vim script #884 and that the +This comment line tells getscript.mnv to check MNV script #884 and that the script is automatically installable. Getscript will also use this line to -help build the GetLatestVimScripts.dat file, by including a line such as: > +help build the GetLatestMNVScripts.dat file, by including a line such as: > - 884 1 :AutoInstall: AutoAlign.vim + 884 1 :AutoInstall: AutoAlign.mnv < -assuming that such a line isn't already in GetLatestVimScripts.dat file. -See |glvs-plugins| for more. Thus, GetLatestVimScripts thus provides a +assuming that such a line isn't already in GetLatestMNVScripts.dat file. +See |glvs-plugins| for more. Thus, GetLatestMNVScripts thus provides a comprehensive ability to keep your plugins up-to-date! In summary: * Optionally tell getscript that it is allowed to build/append a - GetLatestVimScripts.dat file based upon already installed plugins: > - let g:GetLatestVimScripts_allowautoinstall=1 + GetLatestMNVScripts.dat file based upon already installed plugins: > + let g:GetLatestMNVScripts_allowautoinstall=1 < * A line such as > - " GetLatestVimScripts: 884 1 :AutoInstall: AutoAlign.vim + " GetLatestMNVScripts: 884 1 :AutoInstall: AutoAlign.mnv < in an already-downloaded plugin constitutes the concurrence of the plugin author that getscript may do AutoInstall. Not all plugins may be AutoInstall-able, and the plugin's author is best situated to know whether or not his/her plugin will AutoInstall properly. * A line such as > - 884 1 :AutoInstall: AutoAlign.vim -< in your GetLatestVimScripts.dat file constitutes your permission + 884 1 :AutoInstall: AutoAlign.mnv +< in your GetLatestMNVScripts.dat file constitutes your permission to getscript to do AutoInstall. AutoInstall requires both your - and the plugin author's permission. See |GetLatestVimScripts_dat|. + and the plugin author's permission. See |GetLatestMNVScripts_dat|. - *GetLatestVimScripts_dat* -As an example of a <GetLatestVimScripts.dat> file: + *GetLatestMNVScripts_dat* +As an example of a <GetLatestMNVScripts.dat> file: > ScriptID SourceID Filename -------------------------- - 294 1 :AutoInstall: Align.vim - 120 2 Decho.vim + 294 1 :AutoInstall: Align.mnv + 120 2 Decho.mnv 40 3 DrawIt.tar.gz - 451 4 EasyAccents.vim - 195 5 engspchk.vim - 642 6 GetLatestVimScripts.vim - 489 7 Manpageview.vim + 451 4 EasyAccents.mnv + 195 5 engspchk.mnv + 642 6 GetLatestMNVScripts.mnv + 489 7 Manpageview.mnv < Note: the first two lines are required, but essentially act as comments. ============================================================================== -5. GetLatestVimScripts Friendly Plugins *getscript-plugins* *glvs-plugins* +5. GetLatestMNVScripts Friendly Plugins *getscript-plugins* *glvs-plugins* (this section is for plugin authors)~ If a plugin author includes the following comment anywhere in their plugin, -GetLatestVimScripts will find it and use it to automatically build the user's -GetLatestVimScripts.dat files: +GetLatestMNVScripts will find it and use it to automatically build the user's +GetLatestMNVScripts.dat files: > src_id v - " GetLatestVimScripts: ### ### yourscriptname + " GetLatestMNVScripts: ### ### yourscriptname ^ scriptid < @@ -227,45 +227,45 @@ are, then you may include :AutoInstall: just before "yourscriptname": > src_id v - " GetLatestVimScripts: ### ### :AutoInstall: yourscriptname + " GetLatestMNVScripts: ### ### :AutoInstall: yourscriptname ^ scriptid < NOTE: The :AutoInstall: feature requires both the plugin author's and~ the user's permission to operate!~ -GetLatestVimScripts commands for those scripts are then appended, if not -already present, to the user's GetLatest/GetLatestVimScripts.dat file. It is +GetLatestMNVScripts commands for those scripts are then appended, if not +already present, to the user's GetLatest/GetLatestMNVScripts.dat file. It is a relatively painless way to automate the acquisition of any scripts your plugins depend upon. -Now, as an author, you probably don't want GetLatestVimScripts to download +Now, as an author, you probably don't want GetLatestMNVScripts to download your own scripts atop your own copy, thereby overwriting your not-yet-released -hard work. GetLatestVimScripts provides a solution for this: put +hard work. GetLatestMNVScripts provides a solution for this: put > 0 0 yourscriptname < -into your <GetLatestVimScripts.dat> file and GetLatestVimScripts will skip -examining the "yourscriptname" scripts for those GetLatestVimScripts comment +into your <GetLatestMNVScripts.dat> file and GetLatestMNVScripts will skip +examining the "yourscriptname" scripts for those GetLatestMNVScripts comment lines. As a result, those lines won't be inadvertently installed into your -<GetLatestVimScripts.dat> file and subsequently used to download your own +<GetLatestMNVScripts.dat> file and subsequently used to download your own scripts. This is especially important to do if you've included the :AutoInstall: option. Be certain to use the same "yourscriptname" in the "0 0 yourscriptname" line -as you've used in your GetLatestVimScripts comment! +as you've used in your GetLatestMNVScripts comment! ============================================================================== -6. GetLatestVimScripts AutoInstall *getscript-autoinstall* +6. GetLatestMNVScripts AutoInstall *getscript-autoinstall* *glvs-autoinstall* -GetLatestVimScripts now supports "AutoInstall". Not all scripts are +GetLatestMNVScripts now supports "AutoInstall". Not all scripts are supportive of auto-install, as they may have special things you need to do to install them (please refer to the script's "install" directions). On the other hand, most scripts will be auto-installable. -To let GetLatestVimScripts do an autoinstall, the data file's comment field +To let GetLatestMNVScripts do an autoinstall, the data file's comment field should begin with (surrounding blanks are ignored): > :AutoInstall: @@ -274,107 +274,107 @@ Both colons are needed, and it should begin the comment (yourscriptname) field. One may prevent any autoinstalling by putting the following line in your -<.vimrc>: > +<.mnvrc>: > - let g:GetLatestVimScripts_allowautoinstall= 0 + let g:GetLatestMNVScripts_allowautoinstall= 0 < With :AutoInstall: enabled, as it is by default, files which end with - ---.tar.bz2 : decompressed & untarred in .vim/ directory - ---.vba.bz2 : decompressed in .vim/ directory, then vimball handles it + ---.tar.bz2 : decompressed & untarred in .mnv/ directory + ---.vba.bz2 : decompressed in .mnv/ directory, then mnvball handles it ---.vmb.bz2 : idem - ---.vim.bz2 : decompressed & moved into .vim/plugin directory - ---.tar.gz : decompressed & untarred in .vim/ directory - ---.vba.gz : decompressed in .vim/ directory, then vimball handles it + ---.mnv.bz2 : decompressed & moved into .mnv/plugin directory + ---.tar.gz : decompressed & untarred in .mnv/ directory + ---.vba.gz : decompressed in .mnv/ directory, then mnvball handles it ---.vmb.gz : idem - ---.vim.gz : decompressed & moved into .vim/plugin directory - ---.vba : moved to .vim/ directory, then vimball handles it + ---.mnv.gz : decompressed & moved into .mnv/plugin directory + ---.vba : moved to .mnv/ directory, then mnvball handles it ---.vmb : idem - ---.vim : moved to .vim/plugin directory - ---.zip : unzipped in .vim/ directory + ---.mnv : moved to .mnv/plugin directory + ---.zip : unzipped in .mnv/ directory and which merely need to have their components placed by the untar/gunzip or -move-to-plugin-directory process should be auto-installable. Vimballs, of +move-to-plugin-directory process should be auto-installable. MNVballs, of course, should always be auto-installable. When is a script not auto-installable? Let me give an example: - .vim/after/syntax/blockhl.vim + .mnv/after/syntax/blockhl.mnv -The <blockhl.vim> script provides block highlighting for C/C++ programs; it is +The <blockhl.mnv> script provides block highlighting for C/C++ programs; it is available at: - https://www.vim.org/scripts/script.php?script_id=104 + https://www.mnv.org/scripts/script.php?script_id=104 -Currently, vim's after/syntax only supports by-filetype scripts (in -blockhl.vim's case, that's after/syntax/c.vim). Hence, auto-install would -possibly overwrite the current user's after/syntax/c.vim file. +Currently, mnv's after/syntax only supports by-filetype scripts (in +blockhl.mnv's case, that's after/syntax/c.mnv). Hence, auto-install would +possibly overwrite the current user's after/syntax/c.mnv file. -In my own case, I use <aftersyntax.vim> (renamed to after/syntax/c.vim) to +In my own case, I use <aftersyntax.mnv> (renamed to after/syntax/c.mnv) to allow a after/syntax/c/ directory: - https://www.vim.org/scripts/script.php?script_id=1023 + https://www.mnv.org/scripts/script.php?script_id=1023 The script allows multiple syntax files to exist separately in the -after/syntax/c subdirectory. I can't bundle aftersyntax.vim in and build an +after/syntax/c subdirectory. I can't bundle aftersyntax.mnv in and build an appropriate tarball for auto-install because of the potential for the -after/syntax/c.vim contained in it to overwrite a user's c.vim. +after/syntax/c.mnv contained in it to overwrite a user's c.mnv. ============================================================================== -7. GetLatestVimScripts Options *glvs-options* +7. GetLatestMNVScripts Options *glvs-options* > - g:GetLatestVimScripts_wget + g:GetLatestMNVScripts_wget < default= "wget" This variable holds the name of the command for obtaining scripts. > - g:GetLatestVimScripts_options + g:GetLatestMNVScripts_options < default= "-q -O" This variable holds the options to be used with the - g:GetLatestVimScripts_wget command. + g:GetLatestMNVScripts_wget command. > - g:GetLatestVimScripts_allowautoinstall + g:GetLatestMNVScripts_allowautoinstall < default= 1 - This variable indicates whether GetLatestVimScripts is allowed + This variable indicates whether GetLatestMNVScripts is allowed to attempt to automatically install scripts. Furthermore, the plugin author has to have explicitly indicated that his/her plugin is automatically installable (via the :AutoInstall: - keyword in the GetLatestVimScripts comment line). + keyword in the GetLatestMNVScripts comment line). > - g:GetLatestVimScripts_autoinstalldir -< default= $HOME/.vim (linux) - default= $HOME/vimfiles (windows) + g:GetLatestMNVScripts_autoinstalldir +< default= $HOME/.mnv (linux) + default= $HOME/mnvfiles (windows) Override where :AutoInstall: scripts will be installed. - Doesn't override vimball installation. + Doesn't override mnvball installation. > - g:GetLatestVimScripts_scriptaddr -< default='https://www.vim.org/scripts/script.php?script_id=' + g:GetLatestMNVScripts_scriptaddr +< default='https://www.mnv.org/scripts/script.php?script_id=' > - g:GetLatestVimScripts_downloadaddr -< default='https://www.vim.org/scripts/download_script.php?src_id=' + g:GetLatestMNVScripts_downloadaddr +< default='https://www.mnv.org/scripts/download_script.php?src_id=' > - g:GetLatestVimScripts_bunzip2 + g:GetLatestMNVScripts_bunzip2 < default= bunzip2 This variable holds the name of the command to decompress .bz2 files > - g:GetLatestVimScripts_bunzip3 + g:GetLatestMNVScripts_bunzip3 < default= bunzip3 This variable holds the name of the command to decompress .bz3 files > - g:GetLatestVimScripts_gunzip + g:GetLatestMNVScripts_gunzip < default= gunzip This variable holds the name of the command to decompress .gz files > - g:GetLatestVimScripts_unxz + g:GetLatestMNVScripts_unxz < default= unxz This variable holds the name of the command to decompress .xz files > - g:GetLatestVimScripts_unzip + g:GetLatestMNVScripts_unzip < default= unzip This variable holds the name of the command to decompress .zip files @@ -383,32 +383,32 @@ Note: The variables associated with decompression commands help workaround crossplatform issues. For example, on Windows is possible to delegate this calls into `wsl` by doing: > - let g:GetLatestVimScripts_bunzip2= "wsl -e bunzip2" - let g:GetLatestVimScripts_gunzip= "wsl -e gunzip" - let g:GetLatestVimScripts_unxz= "wsl -e unxz" - let g:GetLatestVimScripts_unzip= "wsl -e unzip" + let g:GetLatestMNVScripts_bunzip2= "wsl -e bunzip2" + let g:GetLatestMNVScripts_gunzip= "wsl -e gunzip" + let g:GetLatestMNVScripts_unxz= "wsl -e unxz" + let g:GetLatestMNVScripts_unzip= "wsl -e unzip" < ============================================================================== -8. GetLatestVimScripts Algorithm *glvs-algorithm* *glvs-alg* +8. GetLatestMNVScripts Algorithm *glvs-algorithm* *glvs-alg* -The Vim sourceforge page dynamically creates a page by keying off of the +The MNV sourceforge page dynamically creates a page by keying off of the so-called script-id. Within the webpage of - https://www.vim.org/scripts/script.php?script_id=40 + https://www.mnv.org/scripts/script.php?script_id=40 is a line specifying the latest source-id (src_id). The source identifier numbers are always increasing, hence if the src_id is greater than the one -recorded for the script in GetLatestVimScripts then it's time to download a +recorded for the script in GetLatestMNVScripts then it's time to download a newer copy of that script. -GetLatestVimScripts will then download the script and update its internal +GetLatestMNVScripts will then download the script and update its internal database of script ids, source ids, and scriptnames. The AutoInstall process will: Move the file from GetLatest/ to the following directory - Unix : $HOME/.vim - Windows: $HOME\vimfiles + Unix : $HOME/.mnv + Windows: $HOME\mnvfiles if the downloaded file ends with ".bz2" bunzip2 it else if the downloaded file ends with ".bz3" @@ -419,21 +419,21 @@ The AutoInstall process will: unzip it else if the resulting file ends with ".tar" tar -oxvf it - else if the resulting file ends with ".vim" + else if the resulting file ends with ".mnv" move it to the plugin subdirectory ============================================================================== -9. GetLatestVimScripts History *getscript-history* *glvs-hist* {{{1 +9. GetLatestMNVScripts History *getscript-history* *glvs-hist* {{{1 v38 Feb 25, 2025 : * handles additional decompression option for .bzip3 files. -v37 Sep 23, 2024 : * Support for the new vimball's .vmb extension (old .vba +v37 Sep 23, 2024 : * Support for the new mnvball's .vmb extension (old .vba extension conflicted with visual basic). * Support for |glvs-autoinstall| in ftplugins and packages. * Allow platform driven customization of decompressing commands. -v36 Apr 22, 2013 : * (glts) suggested use of plugin/**/*.vim instead of - plugin/*.vim in globpath() call. +v36 Apr 22, 2013 : * (glts) suggested use of plugin/**/*.mnv instead of + plugin/*.mnv in globpath() call. * (Andy Wokula) got warning message when setting g:loaded_getscriptPlugin v35 Apr 07, 2012 : * (MengHuan Yu) pointed out that the script URL has @@ -446,12 +446,12 @@ v33 May 31, 2011 : * using fnameescape() instead of escape() * *.xz support v32 Jun 19, 2010 : * (Jan Steffens) added support for xz compression v31 Jun 29, 2008 : * (Bill McCarthy) fixed having hls enabled with getscript - * (David Schaefer) the acd option interferes with vimballs + * (David Schaefer) the acd option interferes with mnvballs Solution: bypass the acd option v30 Jun 13, 2008 : * GLVS now checks for existence of fnameescape() and will issue an error message if it is not supported v29 Jan 07, 2008 : * Bram M pointed out that cpo is a global option and that - getscriptPlugin.vim was setting it but not restoring it. + getscriptPlugin.mnv was setting it but not restoring it. v28 Jan 02, 2008 : * improved shell quoting character handling, cygwin interface, register-a bypass Oct 29, 2007 * Bill McCarthy suggested a change to getscript that avoids @@ -459,13 +459,13 @@ v28 Jan 02, 2008 : * improved shell quoting character handling, cygwin v24 Apr 16, 2007 : * removed save&restore of the fo option during script loading v23 Nov 03, 2006 : * ignores comments (#...) - * handles vimballs + * handles mnvballs v22 Oct 13, 2006 : * supports automatic use of curl if wget is not available v21 May 01, 2006 : * now takes advantage of autoloading. v20 Dec 23, 2005 : * Eric Haarbauer found&fixed a bug with unzip use; unzip needs the -o flag to overwrite. -v19 Nov 28, 2005 : * v18's GetLatestVimScript line accessed the wrong +v19 Nov 28, 2005 : * v18's GetLatestMNVScript line accessed the wrong script! Fixed. v18 Mar 21, 2005 : * bugfix to automatic database construction * bugfix - nowrapscan caused an error @@ -477,27 +477,27 @@ v18 Mar 21, 2005 : * bugfix to automatic database construction the next script (after trying three times to download a script description page) Apr 20, 2005 * bugfix - when a failure to download occurred, - GetLatestVimScripts would stop early and claim that + GetLatestMNVScripts would stop early and claim that everything was current. Fixed. -v17 Aug 25, 2004 : * g:GetLatestVimScripts_allowautoinstall, which +v17 Aug 25, 2004 : * g:GetLatestMNVScripts_allowautoinstall, which defaults to 1, can be used to prevent all :AutoInstall: v16 Aug 25, 2004 : * made execution of bunzip2/gunzip/tar/zip silent * fixed bug with :AutoInstall: use of helptags v15 Aug 24, 2004 : * bugfix: the "0 0 comment" download prevention wasn't always preventing downloads (just usually). Fixed. -v14 Aug 24, 2004 : * bugfix -- helptags was using dotvim, rather than - s:dotvim. Fixed. +v14 Aug 24, 2004 : * bugfix -- helptags was using dotmnv, rather than + s:dotmnv. Fixed. v13 Aug 23, 2004 : * will skip downloading a file if its scriptid or srcid is zero. Useful for script authors; that way their - own GetLatestVimScripts activity won't overwrite + own GetLatestMNVScripts activity won't overwrite their scripts. v12 Aug 23, 2004 : * bugfix - a "return" got left in the distribution that was intended only for testing. Removed, now works. * :AutoInstall: implemented -v11 Aug 20, 2004 : * GetLatestVimScripts is now a plugin: - * :GetLatestVimScripts command - * (runtimepath)/GetLatest/GetLatestVimScripts.dat +v11 Aug 20, 2004 : * GetLatestMNVScripts is now a plugin: + * :GetLatestMNVScripts command + * (runtimepath)/GetLatest/GetLatestMNVScripts.dat now holds scripts that need updating v10 Apr 19, 2004 : * moved history from script to doc v9 Jan 23, 2004 : windows (win32/win16/win95) will use @@ -510,9 +510,9 @@ v7 Sep 02, 2003 : added error messages if "Click on..." or "src_id=" v6 Aug 06, 2003 : final status messages now display summary of work ( "Downloaded someqty scripts" or "Everything was current") - Now GetLatestVimScripts is careful about downloading - GetLatestVimScripts.vim itself! - (goes to <NEW_GetLatestVimScripts.vim>) + Now GetLatestMNVScripts is careful about downloading + GetLatestMNVScripts.mnv itself! + (goes to <NEW_GetLatestMNVScripts.mnv>) v5 Aug 04, 2003 : missing an endif near bottom v4 Jun 17, 2003 : redraw! just before each "considering" message v3 May 27, 2003 : Protects downloaded files from errant shell @@ -526,4 +526,4 @@ v2 May 14, 2003 : extracts name of item to be obtained from the and they became numbers. Fixes comparison. ============================================================================== -vim:tw=78:ts=8:noet:ft=help:fdm=marker +mnv:tw=78:ts=8:noet:ft=help:fdm=marker |